Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9HEUcP39051 for ; Wed, 17 Oct 2001 10:30:38 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9HEUXc26788; Wed, 17 Oct 2001 10:30:33 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Performance problems - Indexes and VACUUM In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Tue, 16 Oct 2001 20:29:50 -0700" Date: Wed, 17 Oct 2001 10:30:33 -0400 Message-ID: <26785.1003329033@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/235 X-Sequence-Number: 5190 "Josh Berkus" 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