Re: Asynchronous Append on postgres_fdw nodes.

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: etsuro(dot)fujita(at)gmail(dot)com
Cc: pryzby(at)telsasoft(dot)com, a(dot)lepikhov(at)postgrespro(dot)ru, movead(dot)li(at)highgo(dot)ca, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Asynchronous Append on postgres_fdw nodes.
Date: 2020-11-20 11:26:47
Message-ID: 20201120.202647.1331088376150329871.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Fri, 20 Nov 2020 20:16:42 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
me> + /* If this was the second part of an async request, we must fetch until NULL. */
me> + if (fsstate->async_aware)
me> + {
me> + /* call once and raise error if not NULL as expected? */
me> + while (PQgetResult(conn) != NULL)
me> + ;
me> + fsstate->conn_state->async_query_sent = false;
me> + }
me>
me> PQgetResult() receives the result of a query at once. This code means
me> several queries (FETCHes) are queued in, and we discard the result
me> except the last one. Actually the res is just PQclear'd just after so
me> this just discards *all* result of maybe more than one FETCHes. I
me> think something's wrong if we need this.

I was wrong, it is worse. That leaks the returned PGresult.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2020-11-20 11:47:37 Re: VACUUM (DISABLE_PAGE_SKIPPING on)
Previous Message Ajin Cherian 2020-11-20 11:23:57 Re: [HACKERS] logical decoding of two-phase transactions