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

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: nunks <nunks(dot)lol(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date: 2018-06-06 18:46:30
Message-ID: 61E35AE9-8569-40C4-8D30-7999E006C0FA@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

References to them persist in system catalogs. Otherwise, dropping a column would require rewriting every row in the table.

--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
https://www.linkedin.com/in/scottribe/

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Moradhassel, Kavian 2018-06-06 18:54:11 Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Previous Message Wells Oliver 2018-06-06 18:43:22 Re: [pgsql-admin] "Soft-hitting" the 1600 column limit