From: | Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: adding partitioned tables to publications |
Date: | 2019-11-04 15:41:40 |
Message-ID: | CA+FpmFeusJ3oDYmoQFk4CW1Z1ZG7RrZ36bFy-hm9Jc4gie-gpw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Amit,
On Fri, 11 Oct 2019 at 08:06, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>
> Thanks for sharing this case. I hadn't considered it, but you're
> right that it should be handled sensibly. I have fixed table sync
> code to handle this case properly. Could you please check your case
> with the attached updated patch?
>
> I was checking this today and found that the behavior doesn't change much
with the updated patch. The tables are still replicated, just that a select
count from parent table shows 0, rest of the partitions including default
one has the data from the publisher. I was expecting more like an error at
subscriber saying the table type is not same.
Please find the attached file for the test case, in case something is
unclear.
--
Regards,
Rafia Sabih
Attachment | Content-Type | Size |
---|---|---|
lr_part_test.txt | text/plain | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-11-04 15:42:19 | Re: Missed check for too-many-children in bgworker spawning |
Previous Message | Euler Taveira | 2019-11-04 15:39:49 | Re: auxiliary processes in pg_stat_ssl |