| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | logical replication of identity sequences |
| Date: | 2022-04-06 13:07:48 |
| Message-ID: | cb3b0915-b16c-fff1-5137-bb98bba59c2d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Identity sequences shouldn't be addressed directly by name in normal
use. Therefore, requiring them to be added directly to publications is
a faulty interface. I think they should be considered included in a
publication automatically when their owning table is. See attached
patch for a sketch. (It doesn't actually work quite yet, but it shows
the idea, I think.)
If we end up keeping the logical replication of sequences feature, I
think something like this should be added, too.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Automatically-replicate-identity-sequences-with-t.patch | text/plain | 4.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2022-04-06 13:17:28 | Re: BufferAlloc: don't take two simultaneous locks |
| Previous Message | Peter Eisentraut | 2022-04-06 13:01:42 | Re: OpenSSL deprectation warnings in Postgres 10-13 |