From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kris Kiger <kris(at)musicrebellion(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: dump contents & missing functions |
Date: | 2003-12-31 16:56:07 |
Message-ID: | 10982.1072889767@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Kris Kiger <kris(at)musicrebellion(dot)com> writes:
> This whole issue arose when I set a default in a table row equal to a
> value that a plpgsql function returns (ie the table default =
> functionname(variable)). However, after exploration of the dump files,
> it appears that pg_restore tries to restore the tables before it
> restores functions...hence I get an error upon restore of the original
> dump, because the function does not yet exist. Does anyone know if the
> ordering of the restore is in fact the problem? Any input is appreciated!
pg_restore has facilities for telling it to restore the dump contents in
a particular order (basically, get a table-of-contents listing and then
edit the listing). I don't think it works to hack the tar file
directly.
Also you could try using development tip pg_dump, which should get the
dump order right to begin with. AFAIK it will work okay with a 7.4
server.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-12-31 17:20:06 | Re: forcing postgresql 7.3 to use crypt passwords |
Previous Message | Ashok Chauhan | 2003-12-31 16:53:13 | data type |