Postgres Pro
Downloads
Home   >   mailing lists

Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit - Mailing list pgsql-admin

From Ron
Subject Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit
Date
Msg-id 44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com
Whole thread Raw
In response to Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit  ("Moradhassel, Kavian" <kmoradha@ciena.com>)
Responses Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
List pgsql-admin
Tree view
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@ciena.com | 385 Terry Fox Drive | Ottawa, ON, K2K 0L1  Canada


+1

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

--
Angular momentum makes the world go 'round.

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Next
From: "David G. Johnston"
Date:
Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit