| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:34:29 |
| Message-ID: | 20190825203429.GB17780@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 25, 2019 at 04:30:38PM -0400, Tom Lane wrote:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-25 20:49:38 | Re: mingw32 floating point diff |
| Previous Message | Tom Lane | 2019-08-25 20:30:38 | Re: Statement timeout in pg_rewind |