Re: pg_restore problem

From: "Jules Alberts" <jules(dot)alberts(at)arbodienst-limburg(dot)nl>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: pg_restore problem
Date: 2002-08-16 07:56:01
Message-ID: 200208160804.g7G847SO009186@artemis.cuci.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On 15 Aug 2002 at 11:45, Tom Lane wrote:
> "Jules Alberts" <jules(dot)alberts(at)arbodienst-limburg(dot)nl> writes:
> > Sorry, I wasn't quite clear. The problem isn't that the references get
> > lost, but that the actual OIDs of the blobs change.
>
> Yes, they will, and there's not anything you can do to prevent it.
> What is supposed to happen is that pg_restore should update your
> CUST_BLOBS table to contain new blob OIDs instead of old ones.
> It builds a map from the old OIDs, which it can see in the dump file, to
> the new ones that get assigned on-the-fly as the blobs are loaded. Then
> it looks through the database for OID columns, and substitutes new blob
> OIDs wherever it can find a match to the list of old OIDs.

Again something learned :-)

I tested it, it works just like you said. Thanks a lot!

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Rob 2002-08-16 08:06:23 Limiting the result set
Previous Message Aurangzeb M. Agha 2002-08-16 04:26:27 Re: BLOBs