From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Hot Standby and DROP DATABASE |
Date: | 2010-02-06 01:25:33 |
Message-ID: | 20100206.102533.109278335.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
While testing Hot Standby, I have encountered strange behavior with
DROP DATABASE command.
1) connect to "test" database at standby via psql
2) issue DROP DATABASE test command to primary
3) session #1 works fine
4) close session #1
5) "test" database dropped on standby
Fromt the manual:
Running DROP DATABASE, ALTER DATABASE ... SET TABLESPACE, or ALTER
DATABASE ... RENAME on primary will generate a log message that will
cause all users connected to that database on the standby to be
forcibly disconnected. This action occurs immediately, whatever the
setting of max_standby_delay.
So it seems at least the behavior is quite different from what the
docs stats. Am I missing something here?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2010-02-06 02:18:58 | Re: Confusion over Python drivers |
Previous Message | Bruce Momjian | 2010-02-06 00:55:15 | Re: VAC FULL/CLUSTER on system catalogs is prone to deadlock |