Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value - Mailing list pgsql-general

From Michael Lewis
Subject Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value
Date
Msg-id CAHOFxGosG-M4uWeGg2dpyJWYegF5iWP7s-nEqjMrKNsp6M7ojA@mail.gmail.com
Whole thread Raw
In response to Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value
List pgsql-general
Is there any advantage to not defining the default on the replica? If it is not a static value and the publishing database will trigger row updates, I could see waiting to set the default until after the table re-write is done, but otherwise there doesn't seem to be any benefit to skipping column defaults on subscribers.

pgsql-general by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value
Next
From: Mark Dilger
Date:
Subject: Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value