From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergio Gabriel Rodriguez <sgrodriguez@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: problems with large objects dump
Date: Thu, 20 Sep 2012 10:35:08 -0400
Message-ID: <16863.1348151708@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMHBdEoS3b7XZ2JWWG+Y71MGpnDJFLM3U0WnFMxvhOe=Oq2q_w@mail.gmail.com>
References: <CAMHBdEoS3b7XZ2JWWG+Y71MGpnDJFLM3U0WnFMxvhOe=Oq2q_w@mail.gmail.com>
Sergio Gabriel Rodriguez <sgrodriguez@gmail.com> writes:
> Our production database, postgres 8.4 has an approximate size of 200 GB,
> most of the data are large objects (174 GB), until a few months ago we used
> pg_dump to perform backups, took about 3-4 hours to perform all the
> process. Some time ago the process became interminable, take one or two
> days to process, we noticed that the decay process considerably to startup
> backup of large object, so we had to opt for physical backups.
Hm ... there's been some recent work to reduce O(N^2) behaviors in
pg_dump when there are many objects to dump, but I'm not sure that's
relevant to your situation, because before 9.0 pg_dump didn't treat
blobs as full-fledged database objects. You wouldn't happen to be
trying to use a 9.0 or later pg_dump would you? Exactly what 8.4.x
release is this, anyway?
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, sgrodriguez@gmail.com
Subject: Re: problems with large objects dump
In-Reply-To: <16863.1348151708@sss.pgh.pa.us>
* 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