| From: | Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Ajin Cherian <itsajin(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, osumi(dot)takamichi(at)fujitsu(dot)com |
| Subject: | Re: Logical Replication vs. 2PC |
| Date: | 2021-03-21 09:17:20 |
| Message-ID: | 98a7dbee-3ca6-0ec5-750b-0d2754fbfc5f@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20.03.21 16:14, Amit Kapila wrote:
> Right, but I guess in our case using user-provided GID will conflict
> if we use multiple subscriptions on the same node. So, it is better to
> generate a unique identifier like we are discussing here, something
> like (origin_id of subscription + xid of the publisher). Do you see
> any problem with that?
No, quite the opposite: I'm the one advocating the use of xids to
identify transactions. See my patch for filter_prepare.
Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2021-03-21 09:21:17 | Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace |
| Previous Message | Fabien COELHO | 2021-03-21 08:49:43 | Re: Using COPY FREEZE in pgbench |