| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: [PATCH] Make ON CONFLICT DO NOTHING and ON CONFLICT DO UPDATE consistent |
| Date: | 2023-02-09 10:16:20 |
| Message-ID: | CAJ7c6TN_FJzzEaM8aj7hS3=VKTy2yRNdfeCXXYgDXwf0UwHqMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
```
=# commit;
=# SELECT xmin, xmax, cmin, cmax, * FROM t;
xmin | xmax | cmin | cmax | a | b
------+------+------+------+---+---
731 | 0 | 0 | 0 | 1 | 0
732 | 732 | 1 | 1 | 2 | 0
732 | 732 | 1 | 1 | 3 | 0
```
Oops, you got me :) This of course isn't right - the xmax transaction
is committed but we still see the data, etc.
If we really are going to work on this, this part is going to require more work.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-02-09 10:24:19 | Re: Rework LogicalOutputPluginWriterUpdateProgress (WAS Re: Logical replication timeout ...) |
| Previous Message | Hayato Kuroda (Fujitsu) | 2023-02-09 10:12:03 | RE: Exit walsender before confirming remote flush in logical replication |