| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] add concurrent_abort callback for output plugin |
| Date: | 2021-04-26 01:35:30 |
| Message-ID: | CAHut+PvCuVb59qMO8xo_jwxF3+we3fUucVPNw=m6KW1MuVkDdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
While testing another WIP patch [1] a clashing GID problem was found,
which gives us apply worker errors like:
2021-04-26 10:07:12.883 AEST [22055] ERROR: transaction identifier
"pg_gid_16403_608" is already in use
2021-04-26 10:08:05.149 AEST [22124] ERROR: transaction identifier
"pg_gid_16403_757" is already in use
These GID clashes were traced back to a problem of the
concurrent-abort logic: when "streaming" is enabled the
concurrent-abort logic was always sending "prepare" even though a
"stream_prepare" had already been sent.
PSA a patch to correct this.
Kind Regards,
Peter Smith.
Fujitsu Australia
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-concurrent-abort-for-when-streaming.patch | application/octet-stream | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2021-04-26 02:29:16 | comment typo - misnamed function |
| Previous Message | houzj.fnst@fujitsu.com | 2021-04-26 01:30:18 | RE: Parallel INSERT SELECT take 2 |