Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
От
Tom Lane
Тема
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber
Дата
Msg-id
2407667.1634827574@sss.pgh.pa.us
Ответ на
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber (Japin Li)
Список
Дерево обсуждения
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Tom Lane <tgl@sss.pgh.pa.us>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Tom Lane <tgl@sss.pgh.pa.us>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Japin Li <japinli@hotmail.com>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Michael Paquier <michael@paquier.xyz>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Japin Li <japinli@hotmail.com>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Tom Lane <tgl@sss.pgh.pa.us>
Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber Japin Li <japinli@hotmail.com>
Japin Li writes: > On Thu, 21 Oct 2021 at 19:54, Masahiko Sawada wrote: >> BTW I think we can set the parameters from the subscriber side without >> additional network round trips by specifying the "options" parameter >> in the connection string, no? > Yes, we can. However, each client should be concerned the style for > datestyle, IMO it is boring. There's another issue here: the subscriber can run user-defined code (in triggers), while AFAIK the sender cannot. People might be surprised if their triggers run with a datestyle setting different from the database's prevailing setting. So while I think it should be okay to set-and-forget the datestyle on the sender side, we could not get away with that in the subscriber. We'd have to set and unset for each row, much as (e.g.) postgres_fdw has to do. regards, tom lane
В списке pgsql-hackers по дате отправления