pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Jensen <JRJ@ft.fo>
Cc: gspiegelberg@cranel.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Backup is too slow
Date: Sat, 11 Dec 2004 11:37:50 -0500
Message-ID: <16682.1102783070@sss.pgh.pa.us> (raw)
In-Reply-To: <s1b5ccce.070@fs3.ft.fo>
References: <s1b5ccce.070@fs3.ft.fo>

"John Jensen" <JRJ@ft.fo> writes:
> The job is clearly cpu bound in the postmaster process.

Which part of the dump process is CPU bound --- dumping schema, or data?
(Try enabling log_statement for the pg_dump run and correlating the
appearance of queries in the postmaster log with the CPU usage.)

If it's schema-bound, maybe you need to vacuum/analyze your system
catalogs a bit more aggressively.

If it's data-bound, I'm not sure what you can do other than switch to
datatypes that are cheaper to convert to text form.  It would be
interesting to find out where the problem is, though, in case there's
something we can fix for future releases.

			regards, tom lane



view thread (5+ messages)

Message-ID: <16682.1102783070@sss.pgh.pa.us>
Permalink:  ../16682.1102783070@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16682.1102783070@sss.pgh.pa.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, JRJ@ft.fo, gspiegelberg@cranel.com
  Subject: Re: Backup is too slow
  In-Reply-To: <16682.1102783070@sss.pgh.pa.us>
  References: <s1b5ccce.070@fs3.ft.fo> <16682.1102783070@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