| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER DATABASE RENAME with HS/SR |
| Date: | 2010-10-05 08:11:34 |
| Message-ID: | 1286266294.2025.887.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2010-10-05 at 13:29 +0900, Fujii Masao wrote:
> 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
Hot Standby faithfully implements the current behaviour on the master in
that case.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-10-05 08:17:14 | Re: ALTER DATABASE RENAME with HS/SR |
| Previous Message | Heikki Linnakangas | 2010-10-05 08:06:50 | Re: OUTER keyword |