The following bug has been logged online:
Bug reference: 6052
Logged by: dinesh
Email address: dinesh(at)milkorwater(dot)com
PostgreSQL version: 8.4.7
Operating system: WIndows 7 pro 64 bit
Description: ADD COLUMN - ERROR: tables can have at most 1600 columns
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.
After some 1500+ cycles, I get the following error:
ERROR: tables can have at most 1600 columns
SQL state: 54011
Context: SQL statement "ALTER TABLE stage_fo ADD COLUMN exch_ticker char
So it appears that the command
ALTER TABLE stage_fo DROP COLUMN exch_ticker
is only producing some soft effects, not sufficient for the db engine.
There was a similar problem mentioned by another user, Ron St-Pierre, in
-1600-columns). Suggestion made there - to drop/rebuild the table - is not a
I will appreciate any helpful pointers that will get us past this
showstopper. Rewrite is going to be expensive.
Thanks & regards
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2011-06-04 19:50:00|
|Subject: Re: BUG #6049: Can't load dumped view with VALUES and ORDER BY |
|Previous:||From: Kevin Grittner||Date: 2011-06-03 20:25:58|
|Subject: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view|