From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: upgrade path / versioning roles |
Date: | 2005-09-01 18:59:37 |
Message-ID: | 5311.1125601177@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> I tried the fix mentioned in the earlier message to encourage
> validation. Now dumping this "fixed" database, and loadinging it into the
> new database gives:
> ALTER FUNCTION
> psql:./huge.db:4403: ERROR: function plpgsql_validator(oid) does not exist
> CREATE FUNCTION
> ALTER FUNCTION
> psql:./huge.db:4517: ERROR: language "plpgsql" does not exist
> HINT: You need to use "createlang" to load the language into the database.
Ah, right, *that's* why it's a good idea to have the dependency from the
language to the function ;-) ... else there's no guarantee pg_dump will
dump them in the right order. If you want you could add a suitable
pg_depend row.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Allan Wang | 2005-09-01 20:10:54 | rename constraint behavior for duplicate names? |
Previous Message | Tom Lane | 2005-09-01 18:55:45 | Re: Remove xmin and cmin from frozen tuples |