| From: | Jacob Champion <jchampion(at)timescale(dot)com> |
|---|---|
| To: | "shiy(dot)fnst(at)fujitsu(dot)com" <shiy(dot)fnst(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "wangw(dot)fnst(at)fujitsu(dot)com" <wangw(dot)fnst(at)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, vignesh C <vignesh21(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, "Takamichi Osumi (Fujitsu)" <osumi(dot)takamichi(at)fujitsu(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com> |
| Subject: | Re: Data is copied twice when specifying both child and parent table in publication |
| Date: | 2023-03-31 23:05:37 |
| Message-ID: | aac751af-29b4-ca7a-2360-494bc1344cb9@timescale.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/31/23 03:04, shiy(dot)fnst(at)fujitsu(dot)com wrote:
> I noticed that a similar problem has been discussed in this thread, see [1] [2]
> [3] [4].
Ah, thank you. I didn't go far back enough in the thread...
> It seems complicated to fix it if we want to automatically skip tables
> that have been synchronized previously by code
I agree, this is looking very complex. I need to read through the
examples you sent more closely.
> and this may overkill in some
> cases (e.g. The target table in subscriber is not a partitioned table, and the
> user want to synchronize all data in the partitioned table from the publisher).
Hm. It seems like the setup process doesn't really capture the user's
intent. There are just so many things that they could be theoretically
trying to do.
> Besides, it seems not a common case. So I'm not sure we should fix it. Maybe we
> can just add some documentation for it as Peter mentioned.
I think we should absolutely document the pitfalls here. (I'm still
trying to figure out what they are, though, so I don't have any concrete
suggestions yet...)
Thanks!
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-03-31 23:13:00 | Re: regression coverage gaps for gist and hash indexes |
| Previous Message | Jacob Champion | 2023-03-31 23:04:37 | Re: Data is copied twice when specifying both child and parent table in publication |