| From: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Infinite loop in pgbench when running COPY command |
| Date: | 2025-10-02 09:04:56 |
| Message-ID: | CAO6_XqoF9TsEmX=A1sVQjvu6jC-UpeoQVOkhozwCy52_Jm2Pmw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 2, 2025 at 10:27 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Fun. It seems like nobody has ever tested this scenario, even for a
> COPY TO. Why did you try that? Did you have a benchmark scenario in
> mind?
I was trying to trigger pipeline errors while reviewing the
--continue-client-on-abort pgbench patch. And from past experience,
mixing pipelining and COPY is a good way to trigger those.
> That sounds like a good choice to just fail for the time being, all
> these result types don't seem to work (quickly checked). If somebody
> wants to support this case, we could always sort it out, but I am
> ready to bet that the odds are in the favor of doing nothing.
Yeah, that was also my take.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2025-10-02 09:32:09 | RE: Newly created replication slot may be invalidated by checkpoint |
| Previous Message | Amit Kapila | 2025-10-02 08:49:28 | Re: Patch for migration of the pg_commit_ts directory |