pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Dutcher <dave@tridecap.com>
To: 'Piñeiro' <apinheiro@igalia.com>
To: pgsql-performance@postgresql.org
Subject: Re: Performance problem with Sarge compared with Woody
Date: Mon, 11 Sep 2006 14:02:17 -0500
Message-ID: <002801c6d5d4$cd869490$8300a8c0@tridecap.com> (raw)
In-Reply-To: <1157998456.7540.15.camel@codfix.local.igalia.com>

> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org 
> [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Piñeiro
> Subject: [PERFORM] Performance problem with Sarge compared with Woody

> a week ago we migrate a Woody(postgre 7.2.1) server to Sarge(postgre
> 7.4.7). To migrate the database we use a dump, using pg_dump with this
> options:
> pg_dump -U <username> -c -F p -O -v -f <filename> <DBname>
> 
> We have a search, that using woody take about 1-2 minutes, but with
> sarge it is executing about 2 hours, and at least it crashes, with a
> message about a temporal file and no more disk space ( i have 
> more than
> a GB of free disk space).
> 
> Any idea ?

The first question is did you run ANALYZE on the new database after
importing your data?  




view thread (11+ messages)  latest in thread

Message-ID: <002801c6d5d4$cd869490$8300a8c0@tridecap.com>
Permalink:  ../002801c6d5d4$cd869490$8300a8c0@tridecap.com/
Also on:    postgresql.org/message-id/002801c6d5d4$cd869490$8300a8c0@tridecap.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: dave@tridecap.com, apinheiro@igalia.com
  Subject: Re: Performance problem with Sarge compared with Woody
  In-Reply-To: <002801c6d5d4$cd869490$8300a8c0@tridecap.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