Re: postgres_fdw: misplaced? comments in connection.c
Etsuro Fujita <etsuro.fujita@gmail.com>
From: Etsuro Fujita <etsuro.fujita@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-10-13T10:15:40Z
Lists: pgsql-hackers
On Tue, Oct 12, 2021 at 1:33 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote: > On Mon, Oct 11, 2021 at 5:05 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote: > > The comments for pgfdw_get_cleanup_result() say this: > > > > * It's not a huge problem if we throw an ERROR here, but if we get into error > > * recursion trouble, we'll end up slamming the connection shut, which will > > * necessitate failing the entire toplevel transaction even if subtransactions > > * were used. Try to use WARNING where we can. > > > > But we don’t use WARNING anywhere in that function. The right place > > for this is pgfdw_exec_cleanup_query()? > > I noticed that pgfdw_cancel_query(), which is called during (sub)abort > cleanup if necessary, also uses WARNING, instead of ERROR, to avoid > the error-recursion-trouble issue. So I think it would be good to > move this to pgfdw_cancel_query() as well as > pgfdw_exec_cleanup_query(). Attached is a patch for that. There seems to be no objections, so I have applied the patch. Best regards, Etsuro Fujita
Commits
-
postgres_fdw: Move comments about elog level in (sub)abort cleanup.
- 7b8237bbecf7 9.6.24 landed
- eb55dcbeed66 10.19 landed
- c5b2d9c2a4d8 11.14 landed
- 48dc8479c1c4 12.9 landed
- cdab0a80d285 13.5 landed
- 419d27b1a28a 14.1 landed
- 8c7be8688309 15.0 landed