Re: Statement timeout in pg_rewind

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Statement timeout in pg_rewind
Date: 2019-08-25 20:30:38
Message-ID: 1767.1566765038@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter <david(at)fetter(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2019-08-25 20:34:29 Re: Statement timeout in pg_rewind
Previous Message Peter Geoghegan 2019-08-25 20:29:09 Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence