pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Blob error after backup and restore [database  > 5.5 Gb.]
3+ messages / 2 participants
[nested] [flat]

* Blob error after backup and restore [database  > 5.5 Gb.]
@ 2005-06-15 03:00 Amrit Angsusingh <amrit@chaiyo.com>
  2005-06-15 03:53 ` Re: Blob error after backup and restore [database > 5.5 Gb.] Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Amrit Angsusingh @ 2005-06-15 03:00 UTC (permalink / raw)
  To: pgsql-admin


I have postgresql data [7.4.3] on fedora 3  which has the size of more than 5 Gb. and also contains blob for reporting. I use the command
pg_dump -Ft -b homc > homc.tar


test.tar > 5.5 Gb.
after I try to restore it in another server which has the same environment [via nfs] and use the command
pg_restore -d test test.tar


The database "test" after restoration has the same data but no blob found . What's wrong with my command?
Amrit
Thailand



----------------------------------------------------------------------------------
http://www.chaiyo.com äªâÂàÁÅì - ¿ÃÕÍÕàÁÅìÃٻẺãËÁè Ê´ãÊ¡ÇèÒà´ÔÁ...



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Blob error after backup and restore [database > 5.5 Gb.]
  2005-06-15 03:00 Blob error after backup and restore [database  > 5.5 Gb.] Amrit Angsusingh <amrit@chaiyo.com>
@ 2005-06-15 03:53 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2005-06-15 03:53 UTC (permalink / raw)
  To: Amrit Angsusingh <amrit@chaiyo.com>; +Cc: pgsql-admin

"Amrit Angsusingh" <amrit@chaiyo.com> writes:
> after I try to restore it in another server which has the same environment [via nfs] and use the command
> pg_restore -d test test.tar
> The database "test" after restoration has the same data but no blob
> found .

Another thought here: what exactly do you mean by "no blob found"?

The current implementation does not try to restore blobs with the same
OIDs they had in the original database --- rather, it loads them up with
whatever OIDs the new backend cares to assign, and then tries to fix up
database columns of OID and LO types to reference the new OIDs instead
of the old ones.

This is obviously pretty fragile, and we are thinking about changing it
for 8.1, but I wonder if you are getting bit because you are doing
something that pg_restore isn't expecting.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Blob error after backup and restore [database > 5.5 Gb.]
@ 2005-06-15 16:38 Amrit Angsusingh <amrit@chaiyo.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Amrit Angsusingh @ 2005-06-15 16:38 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin


The test database is on one of the fedora 3 server and postgresql 7.4.7 [rpm installed] . I back it up with the command 
pg_dump -Ft - b test > test.tar
And once the process finished I transfer it to another server via nfs and restore it with
pg_restore -d test test.tar
I use this process for more than 1 1/2 year without any problem include the blob , but just for a couple of weeks ago the backup database has no blob and I cannot create and save a new blob
data .
Is that because the database is quite big [5.5 Gb] or not?
Amrit
Thailand

"Amrit Angsusingh"  writes:
> after I try to restore it in another server which has the same environment [via nfs] and use the command
> pg_restore -d test test.tar
> The database "test" after restoration has the same data but no blob
> found .

Another thought here: what exactly do you mean by "no blob found"?

The current implementation does not try to restore blobs with the same
OIDs they had in the original database --- rather, it loads them up with
whatever OIDs the new backend cares to assign, and then tries to fix up
database columns of OID and LO types to reference the new OIDs instead
of the old ones.

This is obviously pretty fragile, and we are thinking about changing it
for 8.1, but I wonder if you are getting bit because you are doing
something that pg_restore isn't expecting.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match



----------------------------------------------------------------------------------
http://www.chaiyo.com äªâÂàÁÅì - ¿ÃÕÍÕàÁÅìÃٻẺãËÁè Ê´ãÊ¡ÇèÒà´ÔÁ...



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2005-06-15 16:38 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-06-15 03:00 Blob error after backup and restore [database  > 5.5 Gb.] Amrit Angsusingh <amrit@chaiyo.com>
2005-06-15 03:53 ` Re: Blob error after backup and restore [database > 5.5 Gb.] Tom Lane <tgl@sss.pgh.pa.us>
2005-06-15 16:38 Re: Blob error after backup and restore [database > 5.5 Gb.] Amrit Angsusingh <amrit@chaiyo.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox