| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Antonin Houska <ah(at)cybertec(dot)at> |
| Subject: | Re: Table AM callback for logical decoding support (REPACK CONCURRENTLY) |
| Date: | 2026-11-21 00:00:28 |
| Message-ID: | CAN4CZFNM62WRM9P2AQBe7YNQ+tuYdY1UEx6NDOsPx5YQ7ukO6Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
+ * TABLEAM_SUPPORTS_LOGICAL_DECODING: every change to the relation's rows can
+ * be logically decoded, which needs the AM's resource manager to have an
+ * rm_decode callback. REPACK (CONCURRENTLY) checks this, as it would
+ * otherwise lose the changes made while it runs.
Doesn't it also require filtering (change_useless_for_repack)?
Also, the helper can crash with partitioned tables or views:
CREATE TABLE p (i int PRIMARY KEY, j int) PARTITION BY RANGE (i);
SELECT test_tableam_supports_features('p'::regclass, 1);
server closed the connection unexpectedly
LOG: client backend (PID 965976) was terminated by signal 11:
Segmentation fault
LOG: all server processes terminated; reinitializing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-11-21 00:27:37 | Re: Fix resource leaks in pg_receivewal on LZ4 close failures |
| Previous Message | jian he | 2026-11-21 00:00:00 | Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions |