From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Exclude pg_largeobject form pg_dump |
Date: | 2016-03-08 15:04:54 |
Message-ID: | VisenaEmail.52.847ab3115631be66.15356bce8aa@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
På tirsdag 08. mars 2016 kl. 15:43:37, skrev Adrian Klaver <
adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>>:
On 03/08/2016 01:53 AM, Andreas Joseph Krogh wrote:
> Hi all.
> Is there a way to exclude pg_largeobject from pg_dump? -T pg_largeobject
> doesn't work. I've tried to exclude tables using OID-datatype also but
> that didn't work either.
Well pg_largeobject is a system catalog so pretty sure it cannot be
excluded.
What tables are you trying to exclude with OID?
Do you care about not dumping the pg_largeobject table or not dumping
the data it contains?
I have several tables with OID-columns and I'd like to dump my DB without any
data in pg_largeobject (> 95% of the space is occupied by data in
pg_largeobject).
I've tried to exclude (using -T) the tables containing OID-columns but
pg_largeobject is still dumped containing the data it seems.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Lupi Loop | 2016-03-08 15:09:37 | Windows default directory for client certificates |
Previous Message | Victor Yegorov | 2016-03-08 14:51:07 | Re: Subtract one array from another, both with non-unique elements |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-03-08 15:06:30 | Re: Parallel Aggregate |
Previous Message | Amit Kapila | 2016-03-08 15:04:08 | Re: Relation extension scalability |