From: Tom Lane <tgl@sss.pgh.pa.us>
To: nunks <nunks.lol@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date: Wed, 06 Jun 2018 12:51:56 -0400
Message-ID: <12881.1528303916@sss.pgh.pa.us> (raw)
In-Reply-To: <CACq6szQbQDG6_mThyH32=6J0e99-KdqOrhZMm9QwvGoVFzNbBw@mail.gmail.com>
References: <CACq6szQbQDG6_mThyH32=6J0e99-KdqOrhZMm9QwvGoVFzNbBw@mail.gmail.com>
nunks <nunks.lol@gmail.com> writes:
> I'm trying to support an application in production at work, and for some
> obscure reason the developer made it drop and re-create a column
> periodically.
Not a good idea ...
> I know this is a bad practice (to say the least), and I'm telling them to
> fix it, but after the 1600th drop/add cycle, PostgreSQL starts giving out
> the column limit error:
> ERROR: tables can have at most 1600 columns
Yup. "Dropping" a column just hides it, doesn't make it disappear.
There are a lot of reasons why that's unlikely to change anytime soon.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, nunks.lol@gmail.com
Subject: Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
In-Reply-To: <12881.1528303916@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox