* Tom Lane wrote:
Christian Ullrich<ch...@chrullrich.net> writes:
I tried adding a not-null column in one step and got a collation
error for a different column.
itd=> alter table livedata add column pricechanged timestamp not null default
current_timestamp;
ERROR: no collation was derived for column "whois_b" with collatable type
citext
TIP: Use the COLLATE clause to set the collation explicitly.
That's pretty bizarre, but I can't reproduce it on the basis of the
supplied example:
I tried adding UNIQUE and CHECK constraints too, and still no luck.
Are you sure you're using 9.1.1?
Yes, the EDB x64 Windows build. But I can't reproduce it now, either. I
got that error twice today (out of only two attempts), while doing
basically this:
- Dump database A
- Clear out database B by doing DROP SCHEMA CASCADE; CREATE SCHEMA
- Load dump into database B
- Replace column in B by DROPping it (it was BOOLEAN before) and then
ADDing the new one as a TIMESTAMP
There was no other activity on B while I was doing it.
I just tried doing that again, but it worked several times in a row.
That may be because I changed the type in A in the meantime, so (among
other things) the heap layout before the DROP COLUMN is different now.
I'll give it another try with the original dump tomorrow when I'm back
at work.
--
Christian
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
