On Fri, Jul 10, 2009 at 2:47 PM, Willy-Bas Loos wrote:
> Hi,
>
> Thanks for your answers!
> I'm using 8.1 and 8.2 on windows2003 servers, and it's true that i could
> probably configure them much better.
Note that support for 8.1 on windows is gone, as it is no longer
considered supportable due to
Hi,
Thanks for your answers!
I'm using 8.1 and 8.2 on windows2003 servers, and it's true that i could
probably configure them much better.
We've recently moved to brand new dedicated database servers with pg8.3 on
debian in 2 projects and it has been much easier to configure these
correctly. There
In response to Willy-Bas Loos :
>
> Whenever i start a big action, like inserting millions of recs or doing a
> large update, the autovacuum fires on top of that.
> It has some adverse effects on performance when i need it most. More than
> once a postgres service crashed on me because of it.
> Su
Hi,
On Thursday 09 July 2009 19:25:15 Willy-Bas Loos wrote:
> Whenever i start a big action, like inserting millions of recs or doing a
> large update, the autovacuum fires on top of that.
You can configure autovacuum to use less resources.
http://www.postgresql.org/docs/current/static/runtime-con
Willy-Bas Loos escribió:
> Hi,
>
> Whenever i start a big action, like inserting millions of recs or doing a
> large update, the autovacuum fires on top of that.
> It has some adverse effects on performance when i need it most. More than
> once a postgres service crashed on me because of it.
> Sur
Hi,
Whenever i start a big action, like inserting millions of recs or doing a
large update, the autovacuum fires on top of that.
It has some adverse effects on performance when i need it most. More than
once a postgres service crashed on me because of it.
Sure, it had too little memory, but it wou
