Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get rid of {Push/Pop}OverrideSearchPath #7145

Merged
merged 1 commit into from Sep 5, 2023

Conversation

zhjwpku
Copy link
Contributor

@zhjwpku zhjwpku commented Aug 24, 2023

PushOverrideSearchPath suffers from a vulnerability issue reported by
CVE-2023-2454. Postgres fix this by replacing it with set_config_option, see [1].
It is recommended that out-of-tree code should also update such code though
the "override" mechanism remains for compatibility.

The postgres master branch(i.e. PG 17) recently removed
PushOverrideSearchPath() and PopOverrideSearchPath(), see [2]. So this should
also ease the process when citus decide to support Postgres v17.

This patch also contains some trivial typo fix.

[1]: postgres commit: 681d9e4621aac0a9c71364b6f54f00f6d8c4337f
[2]: postgres commit: 7c5c4e1c0396b0617a6f9b659dd7375fb0bfb9dc

@zhjwpku zhjwpku force-pushed the get_rid_of_override_search_path branch 2 times, most recently from 056b25e to 8b42672 Compare August 24, 2023 08:29
@zhjwpku zhjwpku changed the title get ride of {Push/Pop}OverrideSearchPath get rid of {Push/Pop}OverrideSearchPath Aug 24, 2023
@zhjwpku zhjwpku force-pushed the get_rid_of_override_search_path branch 3 times, most recently from c37c8f9 to 4ba329d Compare August 24, 2023 10:19
@zhjwpku zhjwpku marked this pull request as draft August 30, 2023 10:51
@zhjwpku zhjwpku force-pushed the get_rid_of_override_search_path branch from 4ba329d to d62f124 Compare September 5, 2023 10:38
@zhjwpku zhjwpku marked this pull request as ready for review September 5, 2023 10:39
@codecov
Copy link

codecov bot commented Sep 5, 2023

Codecov Report

Merging #7145 (a0619c7) into main (8eb3360) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head a0619c7 differs from pull request most recent head c98256e. Consider uploading reports for the commit c98256e to get more accurate results

@@            Coverage Diff             @@
##             main    #7145      +/-   ##
==========================================
- Coverage   93.22%   93.21%   -0.01%     
==========================================
  Files         274      274              
  Lines       59327    59235      -92     
==========================================
- Hits        55307    55216      -91     
+ Misses       4020     4019       -1     

@marcocitus marcocitus force-pushed the get_rid_of_override_search_path branch from d62f124 to a0619c7 Compare September 5, 2023 12:43
PushOverrideSearchPath suffers from a vulnerability issue reported
by CVE-2023-2454. Postgres fix this by replacing it with
set_config_option, see [1]. It is recommended that out-of-tree
code should also update such code though the "override" mechanism
remains for compatibility.

The postgres master branch(i.e. PG 17) recently removed
PushOverrideSearchPath() and PopOverrideSearchPath(), see [2].
So this should also ease the process when citus decide to support
Postgres v17.

This patch also contains some trivial typo fix.

[1]: postgres commit: 681d9e4621aac0a9c71364b6f54f00f6d8c4337f
[2]: postgres commit: 7c5c4e1c0396b0617a6f9b659dd7375fb0bfb9dc

Signed-off-by: Zhao Junwang <zhjwpku@gmail.com>
@marcocitus marcocitus force-pushed the get_rid_of_override_search_path branch from a0619c7 to c98256e Compare September 5, 2023 15:28
@marcocitus marcocitus enabled auto-merge (squash) September 5, 2023 15:29
@marcocitus marcocitus merged commit 205b159 into citusdata:main Sep 5, 2023
107 checks passed
@zhjwpku zhjwpku deleted the get_rid_of_override_search_path branch September 6, 2023 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants