Re: Functions in CHECK constraint not getting dumped before
От | Rajesh Kumar Mallah |
---|---|
Тема | Re: Functions in CHECK constraint not getting dumped before |
Дата | |
Msg-id | 401D6339.3080706@trade-india.com обсуждение исходный текст |
Ответ на | Re: Functions in CHECK constraint not getting dumped before tables. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Functions in CHECK constraint not getting dumped before
|
Список | pgsql-general |
Tom Lane wrote:
Yes it did solve that problem.
another problem that i am facing is during pg_dump i get warning
like:
pg_dump: WARNING: owner of function "txtidx_in" appears to be invalid
pg_dump: WARNING: owner of function "txtidx_out" appears to be invalid
pg_dump: WARNING: owner of function "qtxt_in" appears to be invalid
pg_dump: WARNING: owner of function "qtxt_out" appears to be invalid
pg_dump: WARNING: owner of function "mqtxt_in" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_in" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_out" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_consistent" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_compress" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_decompress" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_penalty" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_picksplit" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_union" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_same" appears to be invalid
And in the dump there are lines like:
REVOKE ALL ON FUNCTION txtidx_in(opaque) FROM PUBLIC;
REVOKE ALL ON FUNCTION txtidx_in(opaque) FROM "";
SET SESSION AUTHORIZATION "103"; <---------------------------------
GRANT ALL ON FUNCTION txtidx_in(opaque) TO PUBLIC;
RESET SESSION AUTHORIZATION;
can you pls tell me how to get rid of the warnings and the invalid
id "103" in pg_proc i dont see any reference to SYSID 103
in the columns proowner or the acl columns.
Any other places where i should look?
Regds
Mallah.
It is found that pg_dump does not dump function referred in CHECK constraint definations before dumping the table defination . As a result the tables do not get restored due to lack of defined functions.Is it something that will be worked upon in future ?This is fixed in CVS tip.
Yes it did solve that problem.
another problem that i am facing is during pg_dump i get warning
like:
pg_dump: WARNING: owner of function "txtidx_in" appears to be invalid
pg_dump: WARNING: owner of function "txtidx_out" appears to be invalid
pg_dump: WARNING: owner of function "qtxt_in" appears to be invalid
pg_dump: WARNING: owner of function "qtxt_out" appears to be invalid
pg_dump: WARNING: owner of function "mqtxt_in" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_in" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_out" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_consistent" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_compress" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_decompress" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_penalty" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_picksplit" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_union" appears to be invalid
pg_dump: WARNING: owner of function "gtxtidx_same" appears to be invalid
And in the dump there are lines like:
REVOKE ALL ON FUNCTION txtidx_in(opaque) FROM PUBLIC;
REVOKE ALL ON FUNCTION txtidx_in(opaque) FROM "";
SET SESSION AUTHORIZATION "103"; <---------------------------------
GRANT ALL ON FUNCTION txtidx_in(opaque) TO PUBLIC;
RESET SESSION AUTHORIZATION;
can you pls tell me how to get rid of the warnings and the invalid
id "103" in pg_proc i dont see any reference to SYSID 103
in the columns proowner or the acl columns.
Any other places where i should look?
Regds
Mallah.
regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
В списке pgsql-general по дате отправления: