Re: ALTER DATABASE RENAME with HS/SR

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: ALTER DATABASE RENAME with HS/SR
Date: 2010-10-05 04:29:10
Message-ID: AANLkTim71+ST35=ZkzsqZH8MkSPNxdYikygawA2uyv6x@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 5, 2010 at 3:42 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 can get the following error from those sessions:

=> SELECT current_user;
ERROR: invalid role OID: 16384

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-10-05 05:12:38 Re: Basic JSON support
Previous Message Tom Lane 2010-10-05 04:18:50 Re: is sync rep stalled?