Skip site navigation (1) Skip section navigation (2)

sorry, too many standbys already vs. MaxWalSenders vs. max_wal_senders

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: sorry, too many standbys already vs. MaxWalSenders vs. max_wal_senders
Date: 2010-03-31 03:06:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
After snapshotting my master using hot backup to create a workable
slave instance, I created recovery.conf on the slave and tried to get
it to connect to the master and stream WAL.

This led to the message "sorry, too many standbys already", which did
not immediately clue me in as to what I needed to do to fix the
problem.  Grepping the source code for the error message revealed that
the problem was that MaxWalSenders was zero.  A few seconds further
head-scratching revealed that this was the GUC max_wal_senders, which
I duly increased from 0 to 1, after which it worked.

I think perhaps this error message needs some adjustment.  It should
be reasonably possible to guess the name of the GUC that needs
increasing based on the error message, and it currently isn't.  Also
I'd vote for making the variable name max_wal_senders rather than
MaxWalSenders, but maybe that's being persnicketty.



pgsql-hackers by date

Next:From: Robert HaasDate: 2010-03-31 03:10:18
Subject: Re: pending patch: Re: HS/SR and smart shutdown
Previous:From: Robert HaasDate: 2010-03-31 02:40:29
Subject: master in standby mode croaks

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group