Hi,
I hope this is the right list. I have read through a few pg_dump slow posts
but none of them seem to apply to our case. We have a nice big server
running windows server 2008 and postgres 8.4. The machine does nothing else
and every so often running the nightly backup take 10 to 12 hours to
Hi,
Thanks for all the answers.
I think I need to first look into the windows connection issue (where some
memory pool gets used up and then new connections cannot be made). If that
does not help, upping the ram by a bit might help (at least buy some time).
And looking into tuning the options
Just a thought, but would it not be possible to add a trigger written in
python that makes a connection to another database and does what it needs
to? I have not done this, but if it is possible it should solve your problem
and one that I have. It should allow updates and selects.
I am sure the
it in transaction pooling mode it works
for simple queries, but something goes lost says the programmer (views that
were setup or something).
Any help or pointers would be nice, either on how to make usage less, or on
how to get pooling to work.
Thanks,
Kobus Wolvaardt
P.S. We are growing the users by another
it in transaction pooling mode it works
for simple queries, but something goes lost says the programmer (views that
were setup or something).
Any help or pointers would be nice, either on how to make usage less, or on
how to get pooling to work.
Thanks,
Kobus Wolvaardt
P.S. We are growing the users by another
2009/8/9 Scott Marlowe scott.marl...@gmail.com
On Sun, Aug 9, 2009 at 4:06 AM, Kobus Wolvaardtkobusw...@gmail.com
wrote:
Hi,
We have software deployed on our network that need postgres, we have
server
that hosts the server and all worked fine until we crossed about 200
users.
The
