| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Column Filtering in Logical Replication |
| Date: | 2021-12-10 21:08:24 |
| Message-ID: | 202112102108.2yawji3o55hw@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Dec-10, Alvaro Herrera wrote:
> I thought about this some more and realized that our earlier conclusions
> were wrong or at least inconvenient. I think that the best behavior if
> you drop a column from a table is to remove the column from the
> publication column list, and do nothing else.
> Should be fairly quick to implement ... on it now.
Actually it's not so easy to implement.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"No hay ausente sin culpa ni presente sin disculpa" (Prov. francés)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Zhang | 2021-12-10 21:44:40 | Question about 001_stream_rep.pl recovery test |
| Previous Message | Alvaro Herrera | 2021-12-10 20:02:08 | Re: Column Filtering in Logical Replication |