Re: Initial Schema Sync for Logical Replication

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Kumar, Sachin" <ssetiya(at)amazon(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Initial Schema Sync for Logical Replication
Date: 2023-03-20 04:21:38
Message-ID: CAA4eK1LYqZQWdGo+i1qUvyrz0FMcrgTQn6PMhLg7pSVhqW71sQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 16, 2023 at 10:27 PM Kumar, Sachin <ssetiya(at)amazon(dot)com> wrote:
>
> > Hi,
> >
> > I have a couple of questions.
> >
> > Q1.
> >
> > What happens if the subscriber already has some tables present? For
> > example, I did not see the post saying anything like "Only if the table does
> > not already exist then it will be created".
> >
> My assumption was the if subscriber is doing initial schema sync , It does not have
> any conflicting database objects.
>

Can't we simply error out in such a case with "obj already exists"?
This would be similar to how we deal with conflicting rows with
unique/primary keys.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-03-20 04:54:46 Re: Improve logging when using Huge Pages
Previous Message Hayato Kuroda (Fujitsu) 2023-03-20 04:13:29 RE: Allow logical replication to copy tables in binary format