From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Steve Poe <spoe(at)sfnet(dot)cc> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, emil(at)baymountain(dot)com |
Subject: | Re: Help tuning postgres |
Date: | 2005-10-18 15:18:41 |
Message-ID: | 1129648722.2022.8.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)baymountain(dot)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(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2005-10-18 15:21:37 | Re: Help tuning postgres |
Previous Message | Richard Huxton | 2005-10-18 07:52:15 | Re: Sequential scan on FK join |