Re: Statement timeout in pg_rewind
Alexander Kukushkin <cyberdemn@gmail.com>
From: Alexander Kukushkin <cyberdemn@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: David Fetter <david@fetter.org>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-08-27T08:45:27Z
Lists: pgsql-hackers
Attachments
- pg_rewind-statement_timeout-v2.patch (text/x-patch) patch v2
On Tue, 27 Aug 2019 at 08:36, Michael Paquier <michael@paquier.xyz> wrote: > I'd rather be on the safe side and as we are looking at this at this > area.. Who knows if this logic is going to change in the future and > how it will change. Agree. > Oops, I misread this part. What about a simple wrapper > run_simple_command which checks after PGRES_COMMAND_OK, and frees the > result then? This could be used for the temporary table creation and > when setting synchronous_commit. Done, please see the next version attached. Regards, -- Alexander Kukushkin
Commits
-
Disable timeouts when running pg_rewind with online source cluster
- e9dcbc9c3fb6 9.5.20 landed
- d64789e97cf6 9.6.16 landed
- 19bfa15a8274 10.11 landed
- f51006ea9657 11.6 landed
- e96f524433db 12.0 landed
- be182e4f9e89 13.0 landed