Re: Proposal: Conflict log history table for Logical Replication
| От | Dilip Kumar |
|---|---|
| Тема | Re: Proposal: Conflict log history table for Logical Replication |
| Дата | |
| Msg-id | CAFiTN-uRa==JxvmTk-2nmng5LG4bh0Jj-P0VzUMQP7BsG2TZkw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Proposal: Conflict log history table for Logical Replication (Peter Smith <smithpb2250@gmail.com>) |
| Ответы |
Re: Proposal: Conflict log history table for Logical Replication
|
| Список | pgsql-hackers |
On Fri, Dec 19, 2025 at 11:12 AM Peter Smith <smithpb2250@gmail.com> wrote: > > I didn't mean to suggest we should allow "not logging anywhere". I > only wanted to ask how the user is expected to revert the conflict > logging back to the default after they had set it to something else. Okay understood, thanks for the clarification. > e.g. > > CREATE SUBSCRIPTION mysub2 ... WITH(conflict_log_destination=table) > Now, how to ALTER SUBSCRIPTION to revert that back to default? > > It seems there is no "reset to default" so is the user required to do > this explicitly? > ALTER SUBSCRIPTION mysub2 SET (conflict_log_destination=log); > > Maybe that's fine --- I was just looking for some examples/clarification. Yeah this is the way, IMHO it looks fine to me. -- Regards, Dilip Kumar Google
В списке pgsql-hackers по дате отправления: