From: | Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pgoutput not capturing the generated columns |
Date: | 2023-08-21 07:45:55 |
Message-ID: | A014A25F-5E45-4C75-9095-8E7BBF26ACDC@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks Euler,
Greatly appreciate your inputs.
> Should pgoutput provide a complete row? Probably. If it is an option that defaults to false and doesn't impact performance.
Yes, it would be great if this feature can be implemented.
> The logical replication design decides to compute the generated columns at subscriber side.
If I understand correctly, this approach involves establishing a function on the subscriber's side that emulates the operation executed to derive the generated column values.
If yes, I see one potential issue where disparities might surface between the values of generated columns on the subscriber's side and those computed within Postgres. This could happen if the generated column's value relies on the current_time function.
Please let me know how can we track the feature requests and the discussions around that.
Thanks,
Rajendra.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2023-08-21 07:56:27 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
Previous Message | Drouvot, Bertrand | 2023-08-21 07:33:36 | Re: WIP: new system catalog pg_wait_event |