Re: pg_dump
| От | Justin Clift |
|---|---|
| Тема | Re: pg_dump |
| Дата | |
| Msg-id | 3C5803CB.9066345A@postgresql.org обсуждение исходный текст |
| Ответ на | Re: pg_dump ("Dave Cramer" <Dave@micro-automation.net>) |
| Список | pgsql-jdbc |
Hi Raymund, Someone else had a problem like this ages ago. I think it was caused by a version mismatch between pg_dump and the running database. Is there any change the version of pg_dump you're using is accidentally from a different release of PostgreSQL and getting in the path somehow? btw, which O/S are you on? :-) Regards and best wishes, Justin Clift -----Original Message----- From: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of raymund Sent: Wednesday, January 30, 2002 1:28 AM To: pgsql-jdbc@postgresql.org Subject: [JDBC] pg_dump Hello, I was trying to backup my database in postgresql 7.1 using "pg_dump mbs > mbs.bu". But I encountered an error: getTables(): Select (funcname) for trigger reg_lock returned 0 tuples. Expected 1. Is there something wrong with the trigger I made in the database? I am using plpgsql on my database script. Thanks. raymund -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
В списке pgsql-jdbc по дате отправления: