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,
On Tue, 2010-10-05 at 13:29 +0900, Fujii Masao wrote:
On Tue, Oct 5, 2010 at 3:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
OTOH, we don't have a similar interlock to prevent renaming users
who have active sessions, so maybe we are being overprotective here.
Yep. What is worse is that we can
On Tue, Oct 5, 2010 at 5:11 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Tue, 2010-10-05 at 13:29 +0900, Fujii Masao wrote:
On Tue, Oct 5, 2010 at 3:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
OTOH, we don't have a similar interlock to prevent renaming users
who have active sessions, so
On Mon, Oct 4, 2010 at 12:42 PM, Simon Riggs si...@2ndquadrant.com wrote:
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
On Tue, 2010-10-05 at 08:56 -0400, Robert Haas wrote:
On Mon, Oct 4, 2010 at 12:42 PM, Simon Riggs si...@2ndquadrant.com wrote:
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
On Mon, Oct 4, 2010 at 2:05 AM, Bernd Helmle maili...@oopsware.de wrote:
Our documentation in
http://www.postgresql.org/docs/9.0/interactive/hot-standby.html currently
says the following:
snip
Running DROP DATABASE, ALTER DATABASE ... SET TABLESPACE, or ALTER DATABASE
... RENAME on the
On Mon, Oct 4, 2010 at 7:38 AM, Fujii Masao masao.fu...@gmail.com wrote:
On Mon, Oct 4, 2010 at 2:05 AM, Bernd Helmle maili...@oopsware.de wrote:
Our documentation in
http://www.postgresql.org/docs/9.0/interactive/hot-standby.html currently
says the following:
snip
Running DROP DATABASE,
Robert Haas robertmh...@gmail.com writes:
I understand that we need to disconnect users if the database is
dropped (it's kind of hard to access a database that's not there any
more...) but I'm fuzzy on why we'd need to do that if it is merely
renamed.
I think that modern backends might
On Mon, Oct 4, 2010 at 2:42 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I understand that we need to disconnect users if the database is
dropped (it's kind of hard to access a database that's not there any
more...) but I'm fuzzy on why we'd need to do that
On 10/4/10 10:24 AM, Robert Haas wrote:
I understand that we need to disconnect users if the database is
dropped (it's kind of hard to access a database that's not there any
more...) but I'm fuzzy on why we'd need to do that if it is merely
renamed.
This seems like an unexpected benefit, and
--On 4. Oktober 2010 13:24:37 -0400 Robert Haas robertmh...@gmail.com
wrote:
I understand that we need to disconnect users if the database is
dropped (it's kind of hard to access a database that's not there any
more...) but I'm fuzzy on why we'd need to do that if it is merely
renamed.
Robert Haas robertmh...@gmail.com wrote:
Don't we already have some mechanism for notifying clients of
parameter changes they might care about?
Are you thinking of GUC_REPORT?
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Mon, Oct 4, 2010 at 3:16 PM, Josh Berkus j...@agliodbs.com wrote:
On 10/4/10 10:24 AM, Robert Haas wrote:
I understand that we need to disconnect users if the database is
dropped (it's kind of hard to access a database that's not there any
more...) but I'm fuzzy on why we'd need to do that
On Tue, Oct 5, 2010 at 3:42 AM, Tom Lane t...@sss.pgh.pa.us wrote:
OTOH, we don't have a similar interlock to prevent renaming users
who have active sessions, so maybe we are being overprotective here.
Yep. What is worse is that we can drop users who have active sessions
on the standby. Then we
Our documentation in
http://www.postgresql.org/docs/9.0/interactive/hot-standby.html currently
says the following:
snip
Running DROP DATABASE, ALTER DATABASE ... SET TABLESPACE, or ALTER DATABASE
... RENAME on the primary will generate a WAL entry that will cause all
users connected to that
15 matches
Mail list logo
