On Thu, Jul 7, 2011 at 2:59 PM, David Hartveld
<[email protected]> wrote:
> I've been looking at my log files on master and slave a bit better, after
> having set log_min_messages = debug5. I can see that somehow the master and
> slave don't properly work together: the slave attempts to send some data
> ('sending write/flush/apply') (I'm assuming this is the slaves current
> location in the WAL?) and then 'terminates process due to administrator
> command', while the master is sending data ('write/flush/apply') (the next
> part of the WAL?), and then 'could not send data to the client: Connection
> reset by peer', after which the server process exits. I'm hoping this
> provides you with more information on what is going on. Do point me in the
> right direction if you need me to investigate further. I have attached two
> pieces of the master and slave log files, which should correspond w.r.t.
> their interaction, where you can see the above behavior.
Ah, so synchronous_standby_names is set on the standby.
Please reset that so we are operating asynchronously, then rerun tests
to see if that avoids the error. You'll probably need to fully
re-generate the standby server before doing this.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
