Replicate over pgbouncer?

On Thursday, May 21, 2015, Andomar <andomar@aule.net> wrote:

Hi,

Today I installed pgbouncer. I added a second installation as a hot
standby. Before starting the standby, I configured "recovery.conf" to
connect to pgbouncer.

This results in an error message:

Pooler Error: Unsupported startup parameter: replication

Is it possible to replicate over a connection through pgbouncer?

I'm doubtful. Why do you think you need such a capability?

David J.

I'm doubtful. Why do you think you need such a capability?

For simplicity. If I can replicate through pgbouncer, I'll need only
one open port on the machine. Postgres would just listen on localhost.

If not, I'll have to make Postgres listen on an interface on a different
port.

-Andomar

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

On 5/21/15 12:12 PM, Andomar wrote:

Hi,

Today I installed pgbouncer. I added a second installation as a hot
standby. Before starting the standby, I configured "recovery.conf" to
connect to pgbouncer.

This results in an error message:

Pooler Error: Unsupported startup parameter: replication

Is it possible to replicate over a connection through pgbouncer?

Currently not.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Since you did not specify your O/S and PostgreSQL version, I'll just point
you to the documentation for 9.1.

http://www.postgresql.org/docs/9.1/interactive/different-replication-solutions.html

It looks very much to me like you are trying to use a hammer to turn a
screw. pg_bouncer is not designed for replication. I strongly suggest you
review the url provided and pick the method that best suits your needs.

On Thu, May 21, 2015 at 2:00 PM, Peter Eisentraut <peter_e@gmx.net> wrote:

On 5/21/15 12:12 PM, Andomar wrote:

Hi,

Today I installed pgbouncer. I added a second installation as a hot
standby. Before starting the standby, I configured "recovery.conf" to
connect to pgbouncer.

This results in an error message:

Pooler Error: Unsupported startup parameter: replication

Is it possible to replicate over a connection through pgbouncer?

Currently not.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

Since you did not specify your O/S and PostgreSQL version, I'll just
point you to the documentation for 9.1.

We're using CentOS 6.5 with PostgreSQL 9.4.1.

Like the original post mentioned, we use a hot standby for replication.

The question is whether we can do the hot standby through pgbouncer, or
if we need a separate open port on the database server just for replication.

Cheers,
Andomar

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

You will want to setup your replication user to connect to PostgreSQL
directly. Going through pgBouncer is asking for trouble.

-Joseph Kregloh