Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
Subject: Re: [GENERAL] How to exclude blobs (large objects) from being
 loaded by pg_restore?
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Alanoly Andrews" <alanolya@invera.com>
CC: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: <5a847d77e03244c8aa84f65b98cbc33e@exch1.invera.com>
Date: Sat, 02 May 2015 19:57:17 +0200
Message-ID: <a424fd94-8e5f-4e16-90c3-fa16841a07ec@mm>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

	Alanoly Andrews wrote:

> This table does not occur in the listing produced in step 1 above and so
> cannot be edited out

Yes, pg_largeobject is not mentioned but the TOC should have an entry named
BLOBS, as well as other entries related to each large object.

If "BLOBS" is removed or commented,  pg_restore -L from that list should not
create any large object into the destination database.

As for the table that contain the "lo" column with the references to large
objects, it can be kept or removed from the restore list, it's up to you, but
it does not determine whether blobs are restored or not.

If the table is kept, its "lo" column will have dangling references to
non-existing large objects, but it's irrelevant for pg_restore, as it doesn't
track those references. You can always update that column to NULL after the
load, or ignore it, or drop it, whatever is more convenient.

Best regards,
-- 
Daniel
PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin