|
Re: my schema + sql function: msg#00084db.postgresql.bugs
Marek "Wróbel" <netim@xxxxxxxxxxx> writes: > In my schema : "my" I create sql function > CREATE OR REPLACE FUNCTION my.my_foo(int4) RETURNS varchar AS ' > select k.k_dupa ||coalesce( '' ['' || k.k_number || '']'' ,'''') > from kont k > where k_id = $1; > ' LANGUAGE 'sql'; > table kont is in schema public. > Everythink working ok, but when I try to restore backup system write : > pg_restore: [archiver (db)] could not execute query: ERROR: Relation "kont" > does not exist > pg_restore: *** aborted because of error Probably table "kont" didn't exist when you first created that function? pg_dump isn't very smart about rearranging the order of object creation to handle such dependencies. You'll need to manually adjust the dump order to deal with this. There are options to pg_restore that you can use to change the order in which it reload objects. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Bug #899: pg_dumpall produce erroneous files if the databbase use procedural language.: 00084, pgsql-bugs |
|---|---|
| Next by Date: | Trigger Crashes Database Back End.: 00084, Peter Childs |
| Previous by Thread: | my schema + sql functioni: 00084, Wróbel |
| Next by Thread: | Bug #898: client_encoding can't support GB18030 encoding in postgresql 7.3.1: 00084, pgsql-bugs |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |