From: | "Doug Pinney" <doug(at)fgrp(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | db dump: handling large objects |
Date: | 2001-03-28 22:03:00 |
Message-ID: | 99tn59$4m6$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
is there a good way to handle large objects when backing up a database? the
way it looks is that the large objects are external files on the file system
and are just pointed to by entries in the table. But it looks like when you
dump the database and then try to restore it, the object ids no longer synch
up.
It's been awhile since we had to deal with this problem but now I have to
create a backup plan. How do you properly back up tables with large objects
(for restoring, or for transferring database to a different server)?
--Doug
p.s. or am i missing something? or does recent versions of pgsql handle
this differently?
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Yue | 2001-03-28 22:10:17 | RE: can't read - permissions error (13) |
Previous Message | Bruce Momjian | 2001-03-28 21:56:15 | Re: [HACKERS] Re: [PORTS] pgmonitor and Solaris |