On Tue, Jun 24, 2014 at 10:17:49AM -0700, Tom Lane wrote:
> Josh Berkus <j...@agliodbs.com> writes:
> > On 06/23/2014 03:52 PM, Andres Freund wrote:
> >> True.  Which makes me wonder whether we shouldn't default this to
> >> something non-zero -- even if it is 5 or 10 days.
> > I'd go for even shorter: 48 hours.  I'd suggest 24 hours, but that would
> > trip up some users who just need really long pg_dumps.
> FWIW, I do not think we should have a nonzero default for this.
> We could not safely set it to any value that would be small enough
> to be really useful in the field.
> BTW, has anyone thought about the interaction of this feature with
> prepared transactions?  I wonder whether there shouldn't be a similar but
> separately-settable maximum time for a transaction to stay in the prepared
> state.  If we could set a nonzero default on that, perhaps on the order of
> a few minutes, we could solve the ancient bugaboo that "prepared
> transactions are too dangerous to enable by default".

Added as a TODO item.

  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to