Horton

Re: Statement timeout in pg_rewind

David Fetter <david@fetter.org>

View thread View on postgr.es
From: David Fetter <david@fetter.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Kukushkin <cyberdemn@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-08-25T20:34:29Z
Lists: pgsql-hackers 
On Sun, Aug 25, 2019 at 04:30:38PM -0400, Tom Lane wrote:
> David Fetter <david@fetter.org> writes:
> > Is pg_rewind the only thing that this hits?
> 
> pg_dump has forced statement_timeout to 0 for ages.  If pg_rewind
> is also likely to have a long-running transaction, I don't see any
> good reason for it not to do likewise.

My mistake.

I meant to ask whether, in addition to pg_dump and pg_rewind, there
are other things that should ignore statement_timeout settings.

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Commits

  1. Disable timeouts when running pg_rewind with online source cluster