| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: DROP DATABASE variant that kills active sessions |
| Date: | 2015-10-16 19:38:25 |
| Message-ID: | 20151016193825.GP6851@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-10-16 16:32:25 -0300, Fabrízio de Royes Mello wrote:
> On Fri, Oct 16, 2015 at 4:12 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > I think this would be a useful feature. What would one do about
> > prepared transactions?
> >
>
> Isn't "rollback all prepared" before an option?
Not necessarily - what if shared objects are affected by the
transaction?
I think it's fine to just not support FORCE in that case - I don't think
it's all that common.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-10-16 19:42:15 | Re: proposal: PL/Pythonu - function ereport |
| Previous Message | Pavel Stehule | 2015-10-16 19:34:43 | Re: proposal: DROP DATABASE variant that kills active sessions |