If performance is slowing down, I suggest you run VACUUM or VACUUM ANALYZE
once a day.
In addition, you can turn DBI's AutoCommit (assuming this is what you are
using to connect to Postgres) to on, which will end the transaction block
and unlock the table for VACUUM.
Without knowing your configuration or your performance problem, it is hard
to make any further suggestions.
Mark
Epilogue.net
> Simple.
>
> In my dynamic sites I have sessions tables that get select/update/insert
> allot, So removing as many obstacles from select/update/insert against
"very
> simple" tables will improve the performance.
>
> --------------------------
> Canaan Surfing Ltd.
> Internet Service Providers
> Ben-Nes Michael - Manager
> Tel: 972-4-6991122
> http://sites.canaan.co.il
> --------------------------
>
> ----- Original Message -----
> From: "Martijn van Oosterhout" <kleptog@svana.org>
> To: "Ben-Nes Michael" <miki@canaan.co.il>
> Cc: <pgsql-general@postgresql.org>
> Sent: Wednesday, October 24, 2001 12:13 PM
> Subject: Re: [GENERAL] Disable Transaction - plans ?
>
>
> > On Wed, Oct 24, 2001 at 11:23:49AM +0200, Ben-Nes Michael wrote:
> > > Hi
> > >
> > > Is there any plan to relase a version which allow the user to disable
> the
> > > use of transactions on some of the tables ?
> >
> > And what would be the use of that?
> >
> > Perhaps you should explain your problem because what you are asking not
a
> > solution to anything.
> >
> > HTH,
> > --
> > Martijn van Oosterhout <kleptog@svana.org>
> > http://svana.org/kleptog/
> > > Magnetism, electricity and motion are like a three-for-two special
> offer:
> > > if you have two of them, the third one comes free.
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
