Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date: 2018-06-06 23:15:42
Message-ID: 44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 06/06/2018 01:54 PM, Moradhassel, Kavian wrote:
>
> To my mind, it makes perfect sense for columns to persist in the table
> structure when dropped…the only question I have is whether the column
> would survive a VACUUM FULL?  i.e. if the table is rewritten after the
> column is dropped, would that change things?
>
> *Kav Moradhassel*|Ciena
>
> kmoradha(at)ciena(dot)com <mailto:kmoradha(at)ciena(dot)com> |385 Terry Fox Drive
> | Ottawa, ON, K2K 0L1  Canada
>
> <mailto:wellsoliver(at)gmail(dot)com>

+1

Another solution would be to dump/drop/create/load *just **that table*.

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David G. Johnston 2018-06-06 23:35:20 Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Previous Message Tom Lane 2018-06-06 18:57:07 Re: [pgsql-admin] "Soft-hitting" the 1600 column limit