pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Performance problems - Indexes and VACUUM
Date: Wed, 17 Oct 2001 10:30:33 -0400
Message-ID: <26785.1003329033@sss.pgh.pa.us> (raw)
In-Reply-To: <web-149383@davinci.ethosmedia.com>
References: <web-149383@davinci.ethosmedia.com>

"Josh Berkus" <josh@agliodbs.com> writes:
> 1. INDEXES: I discovered, the hard way, a peculiar problem.  If you drop
> and re-create a table within the same transaction (in a function, for
> example) the indexes do not get dropped completely.

Kinda hard to believe; even if the old indexes were still around, they
wouldn't be considered to apply to the new table.  I think the problem
is something else.  Can you provide a reproducible example of what
you're seeing?

> runs in about 2 seconds right after a VACUUM.
> 	Unfortunately, 6 hours after a VACUUM, the query bogs down.

What has been changing in the meantime?

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <26785.1003329033@sss.pgh.pa.us>
Permalink:  ../26785.1003329033@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26785.1003329033@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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: Performance problems - Indexes and VACUUM
  In-Reply-To: <26785.1003329033@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