| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Cc: | n(dot)kalinin(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18944: Assertion Failure in psql with idle_session_timeout Set |
| Date: | 2025-06-02 23:31:16 |
| Message-ID: | aD40RKgfY4L4wnfL@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jun 02, 2025 at 07:00:26PM +0200, Anthonin Bonnefoy wrote:
> So if that's expected, we may need additional logic to avoid
> increasing piped_syncs when we're after a COPY? On the other hand,
> ignoring the SYNC seems to break the protocol spec expectation that
> "there is one and only one ReadyForQuery sent for each Sync".
Hmm. This stuff stands as it is in the backend COPY code since
c01641f8aed0 from 2003, so there's not much we can do in the backend
or libpq. Adding some specific logic in psql to avoid piped_syncs
seems like the correct move seen from here.
Most of that should be close to ExecQueryAndProcessResults(), don't
you think? That's where we count the number of piped syncs.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-06-03 03:09:29 | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
| Previous Message | Matheus Alcantara | 2025-06-02 22:56:01 | Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1 |