pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: SpaceBallOne <space_ball_one@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Can anyone explain this: duplicate dbs.
Date: Tue, 24 May 2005 23:01:28 -0400
Message-ID: <7665.1116990088@sss.pgh.pa.us> (raw)
In-Reply-To: <4293E17D.8090706@familyhealth.com.au>
References: <BAY14-DAV38E580C92EFF811F1266ACC0E0@phx.gbl>
	<4293E17D.8090706@familyhealth.com.au>

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
>> If I pg_dump that database then create a new database (e.g. "tempdb") 
>> and upload the dump file (thus making a duplicate) then the same query 
>> only takes 190ms !!
>> Vacuum, vacuum analyse, and vacuum full analyse does not seem to have an 
>> impact on these times.

> Damn, for some reason I didn't read that you had already tried vacuum 
> full.

I'm thinking index bloat, and a PG version too old for vacuum full to
recover any index space.  But without any information about PG version
or EXPLAIN ANALYZE results, we're all just guessing.

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <7665.1116990088@sss.pgh.pa.us>
Permalink:  ../7665.1116990088@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/7665.1116990088@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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, space_ball_one@hotmail.com
  Subject: Re: Can anyone explain this: duplicate dbs.
  In-Reply-To: <7665.1116990088@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