| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot standby, dropping a tablespace |
| Date: | 2009-01-26 09:00:14 |
| Message-ID: | 1232960414.2327.1471.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2009-01-26 09:09:49 | Re: Hot standby, dropping a tablespace |
| Previous Message | Simon Riggs | 2009-01-26 08:52:36 | Re: FATAL: could not open relation pg_tblspc/491086/467369/491103: No such file or directory |