From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | AI Rumman <rummandba(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: add column with default value is very slow |
Date: | 2012-09-11 13:59:40 |
Message-ID: | 20120911135939.GA1656@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Sep 11, 2012 at 07:55:24PM +0600, AI Rumman wrote:
> I added the excel file for locks data.
well, it worked, but why didn't you just make it text file, in notepad or
something like this?
> I was surprised to see that while I was updating a single column value for
> all records in a tables, all indexes are locked by the server.
alter table is not locked (At least looking at the pg_locks data you
showed).
this means - it just takes long time.
Please do:
select pg_total_relation_size('entity');
to see how much data it has to rewrite.
for future - just don't do alter table, with default, and not null.
doing it via add column; set default; batch-backfill data, set not null
will take longer but will be done with much shorter locks.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2012-09-11 14:04:06 | Re: add column with default value is very slow |
Previous Message | AI Rumman | 2012-09-11 13:55:24 | Re: add column with default value is very slow |