Re: Pipeline mode and PQpipelineSync()
| От | Boris Kolpackov |
|---|---|
| Тема | Re: Pipeline mode and PQpipelineSync() |
| Дата | |
| Msg-id | boris.20210629160323@codesynthesis.com обсуждение исходный текст |
| Ответ на | Re: Pipeline mode and PQpipelineSync() (Alvaro Herrera <alvaro.herrera@2ndquadrant.com>) |
| Ответы |
Re: Pipeline mode and PQpipelineSync()
|
| Список | pgsql-hackers |
Alvaro Herrera <alvaro.herrera@2ndquadrant.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.
В списке pgsql-hackers по дате отправления: