Re: ERROR: tables can have at most 1600 columns

From: "Scott Marlowe" <smarlowe(at)qwest(dot)net>
To: "Jaime Casanova" <systemguards(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: tables can have at most 1600 columns
Date: 2004-06-28 21:04:06
Message-ID: 1088456646.29695.12.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 2004-06-28 at 14:37, Jaime Casanova wrote:
> Hi all,
>
> There is a way to actually eliminate those dropped tables so they
> don't affect the 1600 columns limit? I know it's very difficult to end
> up with this problem but apparently "it is" posible.
>
You may want to try recreating the table with select into when you're
changing it. Of course, you'll have to recreate all the fks, indexes,
or other dependent objects.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2004-06-28 21:31:11 Re: Seeing uncommitted transactions
Previous Message Patrick Hatcher 2004-06-28 20:54:20 Q: upgrading from 7.4.1 to 7.4.3.