Re: explain plan difference

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ravi Krishna <srkrishna(at)yahoo(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: explain plan difference
Date: 2019-11-04 14:45:26
Message-ID: 5191.1572878726@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ravi Krishna <srkrishna(at)yahoo(dot)com> writes:
>> VACUUM would not change the state of the dropped columns.

> When does it change?

Never, unless you drop and recreate the table. Removing a dropped
column would change the attnums of following columns, which we
can't support because the tableoid+attnum is the only persistent
identifier of a column.

(From memory, operations like VACUUM FULL and CLUSTER will rewrite
dropped columns with NULLs to reduce their storage impact. But they
don't go away.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2019-11-04 14:53:36 Re: v12 and pg_restore -f-
Previous Message Ravi Krishna 2019-11-04 14:32:26 Re: explain plan difference