Re: Hot standby, dropping a tablespace - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot standby, dropping a tablespace
Date
Msg-id 1232960414.2327.1471.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Hot standby, dropping a tablespace  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Hot standby, dropping a tablespace  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Sun, 2009-01-25 at 19:56 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> >> 2. Kill all connections by given user. Hmm, not used for anything, 
> >> actually. Should remove the roleId argument from GetConflictingVirtualXIDs.
> > 
> > No, because we still need to add code to kill-connected-users if we drop
> > role.
> 
> Oh, I see, that's still a todo item. But we don't do that during normal 
> operation, so why should we during recovery?

LOL. Not many systems allow you to continue working after the access has
been removed. But not, as you say, a problem for Hot Standby unless that
changes.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: FATAL: could not open relation pg_tblspc/491086/467369/491103: No such file or directory
Next
From: Simon Riggs
Date:
Subject: Re: Hot standby, dropping a tablespace