Re: Proposal: Conflict log history table for Logical Replication
От | Amit Kapila |
---|---|
Тема | Re: Proposal: Conflict log history table for Logical Replication |
Дата | |
Msg-id | CAA4eK1LHUghZryDPDSpuVx_usomAOrryWwgx3UvuobWohVQHig@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Proposal: Conflict log history table for Logical Replication (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: Proposal: Conflict log history table for Logical Replication
|
Список | pgsql-hackers |
On Wed, Aug 20, 2025 at 11:47 AM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > On Mon, Aug 18, 2025 at 12:25 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > One idea to keep things simple for the first version is that we allow > > users to specify the table_name for storing conflicts but the table > > should be created internally and if the same name table already > > exists, we can give an ERROR. Then we can later extend the > > functionality to even allow storing conflicts in pre-created tables > > with more checks about its schema. > > That's fair too. I am wondering what namespace we should create this > user table in. If we are creating internally, I assume the user should > provide a schema qualified name right? > Yeah, but if not provided then we should create it based on search_path similar to what we do when user created the table from psql. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: