From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Adding Column on Huge Table
Date: Tue, 19 Mar 2019 22:06:12 +0100
Message-ID: <b1cfe8ba-7365-de0d-ba4f-4ca1daeb62f4@gmx.net> (raw)
In-Reply-To: <20190319205251.GC2983@typhoon>
References: <HK0PR03MB2977B9460C4CC7D0383D05BDAD400@HK0PR03MB2977.apcprd03.prod.outlook.com>
<5b26ed21-a7b5-6c1b-af10-10df4d44a4f7@gmail.com>
<20190319205251.GC2983@typhoon>
Alex Balashov schrieb am 19.03.2019 um 21:52:
> My experience is that adding a column is a rather quick operation even
> on quite large tables, _unless_ the column has a default value, in which
> case that default value is set for every row. In that case, the time
> required for the operation converges with that of a mass-UPDATE.
Which has changed with Postgres 11, where adding a default value does not update all rows in the table.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: spam_eater@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Adding Column on Huge Table
In-Reply-To: <b1cfe8ba-7365-de0d-ba4f-4ca1daeb62f4@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox