Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: Avi Weinberg <aviw(at)gilat(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value
Date: 2021-11-09 21:24:00
Message-ID: CAHOFxGosG-M4uWeGg2dpyJWYegF5iWP7s-nEqjMrKNsp6M7ojA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mark Dilger 2021-11-09 21:43:54 Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value
Previous Message Mark Dilger 2021-11-09 16:07:47 Re: Logical Replication - Should Destination Table Columns Be Defined With Default Value