Re: Exclude pg_largeobject form pg_dump

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Exclude pg_largeobject form pg_dump
Date: 2016-03-08 16:04:15
Message-ID: CANu8FiyWeFxyoDeGhC5D636FuuG40_C5zuSwdii8kc5XzbMk-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Tue, Mar 8, 2016 at 11:02 AM, Andreas Joseph Krogh <andreas(at)visena(dot)com>
wrote:

> På tirsdag 08. mars 2016 kl. 16:57:01, skrev Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Andreas Joseph Krogh <andreas(at)visena(dot)com> writes:
> > What I'm looking for is "inverse -b" in an otherwise complete dump. Any
> plans
> > to add that?
>
> [ shrug... ] Nobody ever asked for it before.
>
> regards, tom lane
>
>
> It surely helps testing production-datasets which contain lots of BLOBs
> where one wants to dump the production-data into a test-env. We have >1TB
> databases containing > 95% blobs so it would help us tremendously to have
> this option.
>
> --
> *Andreas Joseph Krogh*
> CTO / Partner - Visena AS
> Mobile: +47 909 56 963
> andreas(at)visena(dot)com
> www.visena.com
> <https://www.visena.com>
>
>

Probably you need to redesign the schema.

Move the blobs to a new/separate child table. Then you can exclude them.

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-03-08 16:10:43 Re: Exclude pg_largeobject form pg_dump
Previous Message Andreas Joseph Krogh 2016-03-08 16:02:45 Re: Exclude pg_largeobject form pg_dump

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-03-08 16:06:47 Re: Odd warning from pg_dump
Previous Message Andreas Joseph Krogh 2016-03-08 16:02:45 Re: Exclude pg_largeobject form pg_dump