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:25:00
Message-ID: 22129.1522211100@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:
> There's also a few of that annoying postgres_fdw thing. Some of my
> critters hit that regularly :(. We need to figure out what's going on
> there.

Yeah, really. I've made several sustained attempts to reproduce that
locally, on every machine I have, without success.

It's weird, because longfin has shown that failure a couple of times,
but I've not been able to reproduce it in manual runs on longfin's host,
which makes little sense. I'm reduced to a theory that the buildfarm
script creates an environment different from manual runs --- but I cannot
see what that would be.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-03-28 04:48:36 Re: pgsql: Fast ALTER TABLE ADD COLUMN with a non-NULL default
Previous Message Simon Riggs 2018-03-28 04:23:08 Re: pgsql: Allow HOT updates for some expression indexes