Postgres Pro
Downloads
Home   >   mailing lists

Re: [pgsql-admin] "Soft-hitting" the 1600 column limit - Mailing list pgsql-admin

From Scott Ribe
Subject Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date
Msg-id 61E35AE9-8569-40C4-8D30-7999E006C0FA@elevated-dev.com
Whole thread Raw
In response to Re: [pgsql-admin] "Soft-hitting" the 1600 column limit  (Wells Oliver <wells.oliver@gmail.com>)
List pgsql-admin
Tree view 
References to them persist in system catalogs. Otherwise, dropping a column would require rewriting every row in the
table.

--
Scott Ribe
scott_ribe@elevated-dev.com
https://www.linkedin.com/in/scottribe/



> On Jun 6, 2018, at 12:43 PM, Wells Oliver <wells.oliver@gmail.com> wrote:
>
> Just curious then, in what meaningful way do dropped columns persist, what are the reasons?
>

pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Next
From: "Moradhassel, Kavian"
Date:
Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 columnlimit