AmitKumar Jain amitj...@synechron.com wrote:
Milen A. Radev wrote:
AmitKumar Jain **:
1. Could any one please suggest me that how can I see the details
of
function through psql prompt.
\df+
(http://www.postgresql.org/docs/current/static/app-psql.html)
\df will only give
Laszlo Nagy wrote:
PostgreSQL 8.3.5, the system is now stable (uptime 10 days).
PostgreSQL stats collector uses 100% CPU forever:
Could you grab a few stack traces from it and post them? Also possibly
useful, leave strace running on the pgstat process for a while and post
the output
PostgreSQL 8.3.5, the system is now stable (uptime 10 days).
PostgreSQL stats collector uses 100% CPU forever:
On Thursday:
last pid: 29509; load averages: 2.36, 2.01,
2.03
up 5+17:28:56 04:02:53
196
I think that I resolved I my problems with vacuum.I started the autovacuum
and daily runs vacuum verbose analyze, and weekly Reindex.
I'm monitoring the database now.
But, my database continues slow.
Googling a while I started to read something about pdflush and dirty_ratio.
Executing the command
Rafael Domiciano escribió:
2008/12/9 Rafael Domiciano rafael.domici...@gmail.com
Maybe Could be Check-Points? I have changed the parameters sometime ago.
Follow:
effective_cache_size = 200MB
checkpoint_segments = 40# in logfile segments, min 1, 16MB
each
On Mittwoch 03 Dezember 2008 Vladimir Rusinov wrote:
Is there any way to disable dumping query parameters to query log? It
would be ok for us, if this would be just UPDATE table SET data=$1
WHERE id=$2 on log, we don't need full text on log files.
I'd like to have that info too. If you run a
