Alvaro Herrera wrote on 06.04.2009 19:39:
If that is a one-time thing, why not create the table with banned as an
integer column and another boolean column (if your INSERTs are properly
listing the column names), then after the import update the boolean to
the casted integer value, drop the integer and rename the boolean?
Actually it seems it would be better to create the table with only the
integer column, and later use ALTER TABLE / TYPE to change it.
Something like
CREATE TABLE foo (banned integer);
-- run inserts
ALTER TABLE foo ALTER banned TYPE bool USING banned::bool;
That way you don't end up with half a table of dead tuples.
Yes I was worrying about that as well.
Didn't know about the cast in the ALTER statement ;)
Pretty cool.
Thomas
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
