Re: postgres_fdw: misplaced? comments in connection.c

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: postgres_fdw: misplaced? comments in connection.c
Date: 2021-10-13 10:15:40
Message-ID: CAPmGK165=w3fL=hNsCqU9c55n+LNAxK781=LD=ewLbTdiYNkMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 12, 2021 at 1:33 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> On Mon, Oct 11, 2021 at 5:05 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2021-10-13 10:43:44 Re: Next Steps with Hash Indexes
Previous Message Aleksander Alekseev 2021-10-13 09:48:08 Re: RFC: compression dictionaries for JSONB