From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER DATABASE RENAME with HS/SR |
Date: | 2010-10-04 16:42:41 |
Message-ID: | 1286210561.2025.688.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2010-10-04 at 20:38 +0900, Fujii Masao wrote:
> >
> > That looks contrary to the documented behavior. Shouldn't i get a forced
> > disconnect on this connection instead?
>
> Probably yes. To do that, ISTM that we should make ALTER DATABASE .. RENAME
> issue something like XLOG_DBASE_RENAME record, and make the standby server
> call ResolveRecoveryConflictWithDatabase() when that record is applied.
> Simon?
Certainly contrary to documented behaviour, thanks for the report.
Question: do we want that documented behaviour, or should we leave it as
is? Probably want to throw a conflict, but it seems worth asking, since
I know for certain I just made up the documented behaviour.
I'll patch if we agree its required.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Aidan Van Dyk | 2010-10-04 17:06:53 | Re: is sync rep stalled? |
Previous Message | Greg Stark | 2010-10-04 16:20:06 | Re: Adding getrusage profiling data to EXPLAIN output |