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-26T13:42:46Z
Lists: pgsql-hackers
Hi, On Mon, 26 Aug 2019 at 06:28, Michael Paquier <michael@paquier.xyz> wrote: > Alexander, it seems to me that we should also consider lock_timeout > and idle_in_transaction_session_timeout (new as of 9.6), no? We could Well, I was thinking about it and came to the conclusion that we are neither taking heavy locks nor explicitly opening a transaction and therefore we can avoid changing them. But maybe you are right, having them set to the safe value shouldn't hurt. > also group the PQexec/PQresultStatus into a simple wrapper which gets > also called by run_simple_query(). I don't think we can use the same wrapper for run_simple_query() and for places where we call a SET, because PQresultStatus() returns PGRES_TUPLES_OK and PGRES_COMMAND_OK respectively. Passing expected ExecStatusType to the wrapper for comparison is looking a bit ugly to me. 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