Thanks for replying!
I do not use autoincrement or serial because the application AS IS
doesn't use it.
Although I share your approach, the project I am currently managing
uses its own approach
to assign primary keys.
For the sake of clarity I write down the stored procedure and the
Is there a way to make it throw SELECTS only to the
slave/s.
backend_weight0 = 0
should do what you want.
I'm still confused about the md5 passwords in master/slave mode?
With just a normal pool everything is okay, however I get a message saying md5
is not supported in master/slave
Hi !
Had the same issue: for each pgpool server's IP adress you need to set
Authentication method to trust in pool_hba.conf if you want pgpool to work
in master/slave mode.
cheers
michael
On Thu, Aug 28, 2008 at 10:27 AM, Glyn Astill [EMAIL PROTECTED]wrote:
Is there a way to make it throw
Supporting md5 auth with pgpool is fundamentally impossible.
1) PostgreSQL send 32bit encryption salt to pgpool
2) pgpool forwards it to client
3) client encrypt password using the salt
4) pgpool forward the encrypted password to PostgreSQL
Problem is, the salt in #1 is a random number and
Supporting md5 auth with pgpool is fundamentally impossible.
1) PostgreSQL send 32bit encryption salt to pgpool
2) pgpool forwards it to client
3) client encrypt password using the salt
4) pgpool forward the encrypted password to PostgreSQL
Problem is, the salt in #1 is
How does pgpool handle distribution of queries when the slaves are lagging,
even if only slightly?
Nothing. It's user's responsibility to manage the lagging when using
Slony-I like async replications. If you don't like async replications,
you could always use pgpool's replication
Sorry for the poor documentations. Actually the settings
for using
master/slave mode is surprisingly simple. If you are
running Slony
master on host foo port 5432 and a slave on host bar port
5433, the
settings for pgpool.conf would look something like:
backend_hostname0 = 'foo'
master_backend_hostname is a directive name for pgpool(I).
I strongly
recommend to use pgpool-II.
Hi Tatsuo,
I can see now that I clicked the link to download pgpoolII then downloaded
pgpoolI by mistake.
Thanks for all the help.
Glyn
Send instant messages to your online friends
Sorry for the poor documentations. Actually the settings for using
master/slave mode is surprisingly simple. If you are running Slony
master on host foo port 5432 and a slave on host bar port 5433, the
settings for pgpool.conf would look something like:
backend_hostname0 = 'foo'
