Custom Domain; migration from 8.4 to 9.1 and COLLATE

From: Evan Carroll <me(at)evancarroll(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Custom Domain; migration from 8.4 to 9.1 and COLLATE
Date: 2012-05-10 16:32:52
Message-ID: CAAiePB4n8oo3dKP8QVWKZ0o-n-xUsfYb9W5uB2b2GwYjb9GaYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is a cross post from: http://dba.stackexchange.com/q/17609/2639

Just recently I upgraded from Postgresql 8.4.11 to 9.1.3. I used
pg_dump in the process. Now I'm getting an error:

> ERROR: no collation was derived for column "vin" with collatable type citext
> HINT: Use the COLLATE clause to set the collation explicitly.

This is a continuation of the [problem that I had
earlier](http://dba.stackexchange.com/q/17604/2639). It seems the fix
suggested in the Release Notes did not catch [custom
domains](http://www.postgresql.org/docs/9.1/interactive/sql-createdomain.html).
It seems as if the [CREATE
DOMAIN](http://www.postgresql.org/docs/8.3/interactive/sql-createdomain.html)
statement in 8.4 didn't even support the `COLLATE` clause.

This is how I created the `vin` type,

CREATE DOMAIN inventory.valid_vin AS citext
CHECK ( inventory.valid_vin( VALUE ) );

How do I best resolve this error?

--
Evan Carroll - me(at)evancarroll(dot)com
System Lord of the Internets
web: http://www.evancarroll.com
ph: 281.901.0011

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guy Helmer 2012-05-10 17:28:00 Re: vacuum, vacuum full and problems releasing disk space
Previous Message Paul Guyot 2012-05-10 16:22:34 Hot strandby fails to restart after pg_subtrans corruption (?)