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

Getting error while running the pg_basebackup through PGBOUNCER #382

Closed
raghavendrajsv opened this issue Apr 8, 2019 · 4 comments
Closed

Getting error while running the pg_basebackup through PGBOUNCER #382

raghavendrajsv opened this issue Apr 8, 2019 · 4 comments
Labels

Comments

@raghavendrajsv
Copy link

@raghavendrajsv raghavendrajsv commented Apr 8, 2019

We are using PGBOUNCER(connection pool mechanisam). PGBOUNCER uses port 5433.

Postgres database port number is 6433. By using port 5433 PGBOUNCER is connecting to postgres port 6433 database.

Now PGBOUNCER is establishing the connections properly but when I try to run the pg_basebackup through port 5433(PGBOUNCER port) we are receiving below error. Please guide me.

/opt/postgres/9.2/bin/pg_basebackup -p 5433 -U postgres -P -v -x --format=tar --gzip --compress=1 --pgdata=- -D /opt/rao

pg_basebackup: could not connect to server: ERROR: Unsupported startup parameter: replication

@Melkij
Copy link

@Melkij Melkij commented Apr 8, 2019

Why you want use connection pool for replication protocol?

@raghavendrajsv
Copy link
Author

@raghavendrajsv raghavendrajsv commented Apr 8, 2019

@cbandy
Copy link

@cbandy cbandy commented May 16, 2019

What is the value of your ignore_startup_parameters?

@petere
Copy link
Contributor

@petere petere commented Aug 3, 2019

Replication connections through PgBouncer are not supported. I'm not sure if there is any sense in supporting that.

@petere petere added the pending-close label Aug 3, 2019
@petere petere closed this Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants