I would like to refresh this problem again. The use case: local automated testing of database migrations. If those migrations ALTER TABLES by adding and dropping columns, at some point the only valid way out of 1600 columns error is to reload database. If this is not a big problem would be nice to solve.
Bug reference: 6052 Logged by: dinesh Email address: dinesh@milkorwater.com PostgreSQL version: 8.4.7 Operating system: WIndows 7 pro 64 bit Description: ADD COLUMN - ERROR: tables can have at most 1600 columns Details:
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 varying"
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.
