I've noticed that if I blow away the contents of a table and then
repopulate, I only get back to good performance with a vacuum full,
instead of just a simple vacuum. Perhaps I'm doing something wrong as
well.....
On Mon, 4 Mar 2002, Ioannis Kappas wrote:
> ... it really does clean the table at midnight and then immediately vacuums
> the table after it.
> What it really does is to populate the table with two hundred thousand of
> entries each day and
> later on the table will be populated with million of entries each day.
> Again at midnight, all the entries from the table are removed and the table
> is vacuumed (I want to make this clear).
>
> Do you think this is the expected behaviour I am getting? Can I do
> something to improve the
> perfrormance? Should I try to find another database that can handle such
> `big?' amount of entries?
> Can I change something on the configuration of the database that will speed
> up the queries?
>
> Thanks a lot,
> Ioannis
>
> At 09:35 04/03/02 -0500, Doug McNaught wrote:
> >Ioannis <Ioannis.Kappas@dante.org.uk> writes:
> >
> > > ....and I really do run vacuum when I clean the table.
> >
> >You should run it more often than that. Any update or delete on the
> >table will result in space that can't be reused until you run VACUUM.
> >PG has to scan all that empty space to make sure there are no valid
> >records in it whenever you do a query.
> >
> >Run it at least every night.
> >
> >-Doug
> >--
> >Let us cross over the river, and rest under the shade of the trees.
> > --T. J. Jackson, 1863
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
