Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Sadhuprasad Patro <b(dot)sadhu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
Date: 2021-10-18 09:27:22
Message-ID: CAFiTN-tw2HVuSEydRYZhJV0EQpfcJSG7hs8X2xYaS1eCpmC61g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 18, 2021 at 1:41 PM Japin Li <japinli(at)hotmail(dot)com> wrote:

> I attached v3 patch that set IntervalStyle to 'postgres' when the
> server backend is walsender, and this problem has gone.

> I test that set IntervalStyle to 'sql_standard' on publisher and
> 'iso_8601' on subscriber, it works fine.

> Please try v3 patch and let me know if they work as unexpected.
> Thanks in advance.

I think the idea of setting the standard DateStyle and the
IntervalStyle on the walsender process looks fine to me. As this will
avoid extra network round trips as Tom mentioned.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-10-18 09:28:58 Re: Data is copied twice when specifying both child and parent table in publication
Previous Message Amit Kapila 2021-10-18 09:07:19 Re: Skipping logical replication transactions on subscriber side