From: Josh Berkus <josh@agliodbs.com>
To: Ron St-Pierre <rstpierre@syscor.com>
To: pgsql-performance@postgresql.org
Subject: Re: Index Problem?
Date: Fri, 16 Apr 2004 10:01:52 -0700
Message-ID: <200404161001.52989.josh@agliodbs.com> (raw)
In-Reply-To: <40800CC2.3050707@syscor.com>
References: <40800CC2.3050707@syscor.com>
Ron,
> The emp table has 60 columns, all indexed, about two-thirds are numeric,
> but they are not affected by this update. The other 50+ columns are
> updated in the middle of the night and the amount of time that update
> takes isn't a concern.
Well, I'd say that you have an application design problem, but that's not what
you asked for help with ;-)
> Late last night I dumped the table, dropped it and re-created it from
> the dump (on the production server - when no one was looking). When I
> re-ran the function it took almost 11 minutes, which was pretty much in
> line with my results from the dev server.
Sounds like you need to run a REINDEX on the table -- and after that,
dramatically increase your max_fsm_pages, and run lazy VACUUM immediately
after the batch update to clean up.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, rstpierre@syscor.com
Subject: Re: Index Problem?
In-Reply-To: <200404161001.52989.josh@agliodbs.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