Re: Hot standby, dropping a tablespace

From: Andres Freund <andres(at)anarazel(dot)de>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot standby, dropping a tablespace
Date: 2009-01-26 10:18:13
Message-ID: 497D8DE5.7020905@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Simon Riggs wrote:
> 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.
Just like around every unixish system?

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2009-01-26 10:20:11 Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Previous Message Simon Riggs 2009-01-26 09:09:49 Re: Hot standby, dropping a tablespace