"D. Dante Lorenso" <dante@lorenso.com> writes: > I did this in my database: > CREATE CAST (VARCHAR AS BYTEA) WITHOUT FUNCTION; > I'm using PostgreSQL 8.2.4 for both the dump and restore database. Why > doesn't the CAST dump and restore? pg_dump thinks it's a built-in system object. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Michael Glaesemann <grzm@seespotcode.net> writes: > On Nov 17, 2007, at 0:36 , Tom Lane wrote: >> pg_dump thinks it's a built-in system object. > What other objects might be susceptible to this? Operators? Operator > classes? It's just casts. They're a bit of a problem since they have neither owners nor schemas, so there's not anything very concrete to base a dump-or-don't-dump decision on. The rule pg_dump uses is to dump it if at least one of the three underlying objects (source type, dest type, or function) is dumpable. Here you've got 2 builtin types and no function, so you lose. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly