From: Alanoly Andrews <alanolya@invera.com>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: How to exclude blobs (large objects) from being loaded by pg_restore?
Date: Fri, 1 May 2015 14:12:08 +0000
Message-ID: <5a847d77e03244c8aa84f65b98cbc33e@exch1.invera.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
Hello,
We have a database that has been unloaded using pg_dump. This database has a table with a field defined as "lo". When restoring this database to another system, we want to avoid loading this particular table as it is very large (about 8GB of blob data) and is not needed on the target system. I tried the following:
1. Create a list of all the tables in the pg_dump file using the -l option of pg_restore
2. Edit out the lines corresponding to the said table (with the "lo" column)
3. Run the pg_restore with the -L option to use the edited list of tables.
I have found that what this does is to exclude only the non-lo fields of the table. So after the load, the table itself is not visible in the target system. But the actual blob data does get loaded since they are contained in the pg_largeobject system table. This table does not occur in the listing produced in step 1 above and so cannot be edited out. Besides it is a system table and should not be excluded anyway.
I'd appreciate some input on how I can get the blob data of a specific table to be excluded from a pg_restore. This is an operation that we need to do on a monthly basis. We do not want to exclude the blobs from the dump itself (since the whole database is to be preserved as a monthly record), but only from the restore.
Postgres 9.1.4 on AIX.
Thanks.
Alanoly Andrews.
Invera Inc.
Montreal, Canada.
________________________________
If you no longer wish to receive any of our emails, click on UNSUBSCRIBE.<mailto:unsubscribe@invera.com?subject=***Unsubscribe***> This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Si vous ne d?sirez plus recevoir de nos courriels, veuillez appuyer sur D?SABONNEMENT.<mailto:unsubscribe@invera.com?subject=***Unsubscribe***> Ce courriel est confidentiel et prot?g?. L'exp?diteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) d?sign?(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser imm?diatement, par retour de courriel ou par un autre moyen.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alanolya@invera.com, pgsql-general@postgresql.org
Subject: Re: How to exclude blobs (large objects) from being loaded by pg_restore?
In-Reply-To: <5a847d77e03244c8aa84f65b98cbc33e@exch1.invera.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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