Skip to content

Added note to the FAQ about SET search_path and pg_dump #5

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added note to the FAQ about SET search_path and pg_dump #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,3 +166,12 @@ servers. Only negative aspect of that is that each PgBouncer hop adds
small amount of latency to each query. So it’s probably best to simply
test whether the payoff is worth the cost.

## `SET search_path` may not work as expected

PgBouncer does not emulate the behaviour of session changing features such as `SET search_path` ([#73](https://github.com/pgbouncer/pgbouncer/pull/73#issuecomment-143957485)),
which means that adjusting this value has a knock-on effect for all clients connected to that database.

Due to [CVE-2018-1058](https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path),
certain versions of `pg_dump` will set an empty `search_path` at runtime, which then breaks any other connections to the database until PgBouncer is restarted ([gitlab-ce #49089](https://gitlab.com/gitlab-org/gitlab-ce/issues/49089)).

If you're using `pg_dump` to backup your databases and are using an affected version mentioned above, you should avoid using `pg_dump` through PgBouncer.