Re: ALTER TABLE ADD COLUMN fast default
Petr Jelinek <petr.jelinek@2ndquadrant.com>
From: Petr Jelinek <petr.jelinek@2ndquadrant.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
Thomas Munro <thomas.munro@enterprisedb.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>, Tom Lane
<tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-02-11T04:20:41Z
Lists: pgsql-hackers
On 09/02/18 06:24, Andrew Dunstan wrote: > On Mon, Feb 5, 2018 at 7:49 AM, Andrew Dunstan > <andrew.dunstan@2ndquadrant.com> wrote: >> On Mon, Feb 5, 2018 at 7:19 AM, Thomas Munro >> <thomas.munro@enterprisedb.com> wrote: >>> On Fri, Jan 26, 2018 at 1:23 PM, Andrew Dunstan >>> <andrew.dunstan@2ndquadrant.com> wrote: >>>> Yeah, thanks. revised patch attached >>> >>> FYI the identity regression test started failing recently with this >>> patch applied (maybe due to commit >>> 533c5d8bddf0feb1785b3da17c0d17feeaac76d8?) >>> >> >> Thanks. Probably the same bug Tomas Vondra found a few days ago. I'm on it. >> > > > Here's a version that fixes the above issue and also the issue with > VACUUM that Tomas Vondra reported. I'm still working on the issue with > aggregates that Tomas also reported. > I see the patch does not update the ALTER TABLE docs section which discusses table rewrites and it seems like it should. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Clean up treatment of missing default and CHECK-constraint records.
- 091e22b2e673 14.0 landed
-
Fast ALTER TABLE ADD COLUMN with a non-NULL default
- 16828d5c0273 11.0 landed
-
Fix application of identity values in some cases
- 533c5d8bddf0 11.0 cited