dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found

Поиск
Список
Период
Сортировка
От Tim Lynch
Тема dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found
Дата
Msg-id 05c701c2d849$6d2b6d50$2c0210ac@loisaida
обсуждение исходный текст
Ответы Re: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: dumpBlobs(): could not open large object: ERROR:  (Robert Treat <xzilla@users.sourceforge.net>)
Список pgsql-admin
version(): PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
redhat 7.3

i've made a backup script, the meat and potatos of which are:

/usr/bin/pg_dump -Fc --blobs -f $dumpdir/$file $dbname

had been working, but recently:
 pg_dump: dumpBlobs(): could not open large object: ERROR:  inv_open: large
object 23312462 not found

for a variety of oids, not NULL or oid 0; over the last few days: 23170697
23208208 23240773 23312462 23318306 23356032 23356728 23495969 23554296
23578064

vacuums okay.

is this from deleting large objects without deleting the oid in a table or
vice versa? pgdump exits non-zero which i guess means the backup is
incomplete.


В списке pgsql-admin по дате отправления:

Предыдущее
От: Robert Treat
Дата:
Сообщение: Re: Unable to run pg_dump from crontab
Следующее
От: radha.manohar@ndsu.nodak.edu
Дата:
Сообщение: Re: Concurrency control in postgresql