The following bug has been logged online: Bug reference: 6052 Logged by: dinesh Email address: din...@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. There was a similar problem mentioned by another user, Ron St-Pierre, in June 2004 (http://bytes.com/topic/postgresql/answers/422107-error-tables-can-have-most -1600-columns). Suggestion made there - to drop/rebuild the table - is not a trivial choice. I will appreciate any helpful pointers that will get us past this showstopper. Rewrite is going to be expensive. Thanks & regards Dinesh Dinesh -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
