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

From Heikki Linnakangas
Subject Re: Hot standby, dropping a tablespace
Date
Msg-id 497CA7D6.90705@enterprisedb.com
Whole thread Raw
In response to Re: Hot standby, dropping a tablespace  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot standby, dropping a tablespace
List pgsql-hackers
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?

>>  I'm thinking of an interface
>> consisting of three functions, replacing the current 
>> GetConflictingVirtualXIDs and ResolveRecoveryConflictWithVirtualXIDs 
>> functions:
> 
> I'm not sure I see any benefit in doing that.

It makes the code more readable.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Next
From: Robert Haas
Date:
Subject: Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)