Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns - Mailing list pgsql-bugs

From Noah Misch
Subject Re: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns
Date
Msg-id 20110607190228.GA15072@tornado.leadboat.com
Whole thread Raw
In response to BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns  ("dinesh" <dinesh@milkorwater.com>)
List pgsql-bugs
On Sat, Jun 04, 2011 at 07:09:27AM +0000, dinesh wrote:
> I have a table which is used during data uploads, a so-called staging table.
> This table has a fixed number of columns that [must] match the input CSV
> file. This CSV file is uploaded using COPY command. Following the COPY, a
> new column (meant for indexing) is constructed on this table using some
> application logic; and dropped after that data upload cycle is over.

When you provide a column list to the COPY command, the table's columns need not
exactly match the input CSV structure.  Could you leave that extra column there
all the time, omit it from your column list in the COPY command, and have a
trigger or default value expression populate it during the COPY?

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #6041: Unlogged table was created bad in slave node
Next
From: Robert Haas
Date:
Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view