From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, yxq <yxq(at)o2(dot)pl>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Re: BUG #14785: Logical replication does not work after adding a column. Bug? |
Date: | 2017-09-25 17:22:52 |
Message-ID: | f78b86da-a9f8-0faa-6117-58d3cc79c1b6@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 25/09/17 18:14, Peter Eisentraut wrote:
> On 9/24/17 16:54, yxq wrote:
>> >>
>> https://www.postgresql.org/message-id/attachment/55041/0001-Handle-heap-rewrites-better-in-logical-replication.patch
>>
>>
>> This fix solves the problem. It would be nice if this or another, better
>> patch in pg10 was implemented.
>
> I would like to commit my patch to PG10, but I'm hoping for an opinion
> from another developer.
>
From my perspective, this is what we should do in PG10. It's similar to
how pglogical handles this situation. Longer term it would be nice if
there was more sane way of identifying and handling the rewrites but
that's not something we can solve at RC time.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2017-09-25 17:32:08 | Re: BUG #14825: enum type: unsafe use? |
Previous Message | randygrolemund | 2017-09-25 17:21:25 | BUG #14828: Security isn't working |