Somehow my previous message got grouped into the Amazon EC2 thread..
I have a problem with fetching from cursors sometimes taking an
extremely long time to run. I am attempting to use the
statement_timeout parameter to limit the runtime on these.
PostgreSQL 8.2.4
Linux 2.6.22.14-72.fc6 #1 SMP W
I have a problem with fetching from cursors sometimes taking an
extremely long time to run. I am attempting to use the
statement_timeout parameter to limit the runtime on these.
PostgreSQL 8.2.4
Linux 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 13:44:07 EST 2007 i686 i686
i386 GNU/Linux
begin;
set searc
Turns out someone had placed a second line further down in the file I
didn't realize was there... So it set it, then reset it.
Thanks,
Joe
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 8:53 AM
To: Hardwick, Joe
Cc: pgsql-general@postgresq
I realize this is very little info to go on but our server had some
trouble this morning..
Postgres 8.2.4
Linux unicron.marketingsolutionsinc.com 2.6.15-1.2054_FC5smp #1 SMP Tue
Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux
PID: 15980 - 2008-04-09 07:49:20 CDT - USER: postgres - DB: maver
I've got a Postgres v8.2.4 server that we recently upped from 2GB RAM to
6GB. I added:
effective_cache_size = 5120MB
to the postgresql.conf file but when I restart the server and do a "show
all" it always comes back with "1000MB". I can set it manually and it
takes but for some reason it just s