| From: | Yambu <hyambu(at)gmail(dot)com> |
|---|---|
| To: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication and truncate table |
| Date: | 2020-12-24 07:24:15 |
| Message-ID: | CALhHtcCNpJBSJuX2TM15Czk0TJx3BRgzbXRt-CM58XS+Lh0+mA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi
We are using Pg V10 , streaming , async
On Wed, Dec 23, 2020 at 7:04 PM Jerry Sievers <gsievers19(at)comcast(dot)net>
wrote:
> Yambu <hyambu(at)gmail(dot)com> writes:
>
> > Hello
> >
> > Please confirm this , truncate a table on master db does not work
> > well wilth logical replication?
> > It results in duplicate key errors on slave right?
>
> Trunc has been supported in native logical replication since V11.
>
> Start by telling us what Pg version you're on and what logical
> replication your using.
>
> See the docs.
> >
> > We should rather use delete from table?
> >
> >
>
> --
> Jerry Sievers
> Postgres DBA/Development Consulting
> e: postgres(dot)consulting(at)comcast(dot)net
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2020-12-24 15:12:48 | Re: Pg_upgrade issue |
| Previous Message | Jerry Sievers | 2020-12-23 17:03:52 | Re: Logical replication and truncate table |