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

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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 06:09:49
Message-ID: CAA8=A7_z8fYpg_nmKLc=EYHeAQY02VP1kyQ1FGhgjF3cBUtiyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Mar 28, 2018 at 3:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
>

Just testing a fix along those lines now.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

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