| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
| Date: | 2012-04-29 15:06:58 |
| Message-ID: | 23364.1335712018@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> In any case, if either the existing session of the TM is cut or it
> cannot create a new connection, it will, after some time, have to give
> up roll back the prepared transactions on the other servers. So some
> kind of setting to not shut down if there are prepared transactions
> pending could be useful. But this could probably be a separate GUC
> setting or two instead of a shutdown mode (or two) of its own.
This argument still seems pretty bogus. The *entire* point of a TM
is to cope with crashes of individual databases under its management.
The proposed setting seems to amount to a "please don't crash" GUC,
which is silly on its face, and does not actually make the TM's life
any easier anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-04-29 15:08:41 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
| Previous Message | Kevin Grittner | 2012-04-29 14:27:29 | Re: Re: xReader, double-effort (was: Temporary tables under hot standby) |