Re: pgsql: Fast ALTER TABLE ADD COLUMN with a non-NULL default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fast ALTER TABLE ADD COLUMN with a non-NULL default
Date: 2018-03-28 04:48:36
Message-ID: 23216.1522212516@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> The one I noticed was:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=treepie&dt=2018-03-28%2002%3A43%3A00
> ...
> which probably is just collation related and will stably fail?

Yeah, magpie is still showing that after the latest commits.
A bit of COLLATE "C" might fix it.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2018-03-28 06:03:38 Re: pgsql: Optimize btree insertions for common case of increasing values
Previous Message Tom Lane 2018-03-28 04:25:00 Re: pgsql: Fast ALTER TABLE ADD COLUMN with a non-NULL default