Re: Logical Replication - behavior of TRUNCATE ... CASCADE - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Logical Replication - behavior of TRUNCATE ... CASCADE
Date
Msg-id CALj2ACW3qGoXXuvZQxv4QEx0W-YRqmkTW-bjyqqYr5Qm7sAmsQ@mail.gmail.com
Whole thread Raw
In response to Re: Logical Replication - behavior of TRUNCATE ... CASCADE  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Fri, May 21, 2021 at 3:39 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
> > Having said that, I see a different use case of such an option which
> > is related to the proposal [1] where the patch provides a truncate
> > option to truncate tables before initial sync. The cascade option
> > could be useful in that feature to resolve some of the PK-FK issues
> > raised in that thread.
>
> Thanks. I will respond in that thread.

Just for the records: I responded with my thoughts at [1].

[1] - https://www.postgresql.org/message-id/CALj2ACUOkYk9WBHLmqEp9JDM333jZXCvqNQnS%3D0ukRdnTOcftg%40mail.gmail.com

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] Add `truncate` option to subscription commands
Next
From: Julien Rouhaud
Date:
Subject: Re: compute_query_id and pg_stat_statements