| From: | Boris Kolpackov <boris(at)codesynthesis(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Pipeline mode and PQpipelineSync() |
| Date: | 2021-06-29 14:14:46 |
| Message-ID: | boris.20210629160323@codesynthesis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> writes:
> No luck reproducing any problems with this sequence as yet.
Can you try to recreate the call flow as implemented here (it's
pretty much plain old C if you ignore error handling):
https://git.codesynthesis.com/cgit/odb/libodb-pgsql/tree/odb/pgsql/statement.cxx?h=bulk#n789
Except replacing `continue` on line 966 with `break` (that will
make the code read-biased which I find triggers the error more
readily, though I was able to trigger it both ways).
Then in an explicit transaction send 500 prepared insert statements
(see previous email for details) with 250'th having a duplicate
primary key.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2021-06-29 14:32:44 | Avoid choose invalid number of partitions (src/backend/executor/nodeAgg.c) |
| Previous Message | Alvaro Herrera | 2021-06-29 13:54:49 | Re: Pipeline mode and PQpipelineSync() |