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

Re: pending patch: Re: HS/SR and smart shutdown

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pending patch: Re: HS/SR and smart shutdown
Date: 2010-04-13 14:16:27
Message-ID: x2i3f0b79eb1004130716rc1c6719aj7c19366d605e1733@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Apr 13, 2010 at 10:27 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Can you explain how to recreate the problem that this patch fixes?

1. Configure and start the primary server.
2. Configure the standby server.
3. Remove all of the WAL files in pg_xlog of the standby.
4. Start the standby.
5. Request smart shutdown against the standby before walreceiver receives any
   WAL records. You would need to emulate the time-consuming authentication
   which usually requires the setting of authentication_timeout. I used the
   attached patch for the emulation. New GUC parameter "wal_sender_sleep" which
   the patch provides for the test specifies the sleep time during walsender's
   handshake processing. If you set it to 10s, walsender sleeps 10 secs before
   it sends the WAL records.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment: test_smart_shutdown_bug_v1.patch
Description: application/octet-stream (1.7 KB)

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2010-04-13 14:18:54
Subject: Re: Hot Standby: Startup at shutdown checkpoint
Previous:From: Robert HaasDate: 2010-04-13 13:27:57
Subject: Re: pending patch: Re: HS/SR and smart shutdown

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