Horton

Re: ALTER TABLE ADD COLUMN fast default

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2021-04-04T19:00:46Z
Lists: pgsql-hackers 
On Sun, Apr 04, 2021 at 02:18:34PM -0400, Andrew Dunstan wrote:
> On 4/4/21 11:21 AM, Andrew Dunstan wrote:
> > On 4/4/21 9:19 AM, Justin Pryzby wrote:
> >> It reminded me of this thread, but nothing ever came of it.
> >> https://www.postgresql.org/message-id/20200328223052.GK20103%40telsasoft.com
> >>
> >> https://www.postgresql.org/message-id/87pmzaq4gx.fsf%40news-spur.riddles.org.uk
> >>
> > I don't recall seeing this. Around that time I was busy returning from
> > Australia at the start of the pandemic, so my I might have missed it in
> > the hubbub.
> 
> If this is still an issue, is it possible to get a self-contained test
> to reproduce it?

Could you follow through with Tim on the other thread ?

-- 
Justin

Commits

  1. Clean up treatment of missing default and CHECK-constraint records.

  2. Fast ALTER TABLE ADD COLUMN with a non-NULL default

  3. Fix application of identity values in some cases