From: Robert Treat <xzilla@users.sourceforge.net>
To: Steve Poe <spoe@sfnet.cc>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org, Csaba Nagy <nagy@ecircle-ag.com>
Cc: emil@baymountain.com
Subject: Re: Help tuning postgres
Date: 18 Oct 2005 11:18:41 -0400
Message-ID: <1129648722.2022.8.camel@camel> (raw)
In-Reply-To: <1129138325.26659.14.camel@amd64-gentoo-laptop>
References: <1129128315.2995.174.camel@coppola.muc.ecircle.de>
<200510121112.11486.emil@baymountain.com>
<1129130273.2995.177.camel@coppola.muc.ecircle.de>
<200510121133.56955.emil@baymountain.com>
<2741.1129137684@sss.pgh.pa.us>
<1129138325.26659.14.camel@amd64-gentoo-laptop>
reindex should be faster, since you're not dumping/reloading the table
contents on top of rebuilding the index, you're just rebuilding the
index.
Robert Treat
emdeon Practice Services
Alachua, Florida
On Wed, 2005-10-12 at 13:32, Steve Poe wrote:
>
> Would it not be faster to do a dump/reload of the table than reindex or
> is it about the same?
>
> Steve Poe
>
> On Wed, 2005-10-12 at 13:21 -0400, Tom Lane wrote:
> > Emil Briggs <emil@baymountain.com> writes:
> > >> Not yet, the db is in production use and I have to plan for a down-time
> > >> for that... or is it not impacting the activity on the table ?
> >
> > > It will cause some performance hit while you are doing it.
> >
> > It'll also lock out writes on the table until the index is rebuilt,
> > so he does need to schedule downtime.
> >
> > regards, tom lane
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
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: xzilla@users.sourceforge.net, spoe@sfnet.cc, tgl@sss.pgh.pa.us, nagy@ecircle-ag.com, emil@baymountain.com
Subject: Re: Help tuning postgres
In-Reply-To: <1129648722.2022.8.camel@camel>
* 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