Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber - Mailing list pgsql-hackers

From Japin Li
Subject Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
Date
Msg-id MEYP282MB1669F58E90835C9BA9CBCF08B6BC9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber  (Michael Paquier <michael@paquier.xyz>)
Responses Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 18 Oct 2021 at 11:59, Michael Paquier <michael@paquier.xyz> wrote:
> On Sun, Oct 17, 2021 at 11:41:35PM -0400, Tom Lane wrote:
>> Ah ... see postgres_fdw's set_transmission_modes().  I think we want
>> to copy that logic not invent some other way to do it.
>
> dblink.c has something similar as of applyRemoteGucs(), except that it
> does not do extra_float_digits.  It would be nice to avoid more
> duplication for those things, at least on HEAD.  On the top of my
> head, don't we have something similar for parallel workers when
> passing down GUCs from the leader?

Since it will be used in more than one places. IMO, we can implement it in core.
Any thoughts?

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
Next
From: Japin Li
Date:
Subject: Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber