BTW, I'm using the pgbadger report to check for peak connections/sessions.
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Huang, Suya
Sent: Friday, July 04, 2014 11:44 AM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] DB sessions
Hi,
We've experienced a DB issue yesterday and after checked the log found that the
peak sessions is 3000 while the peak DB connections is only around 30. The
application is having problem of pulling data but no warnings in DB log as it
doesn't exceed max_connections.
How could this happen? H
Tom Lane writes:
> I'd bet on the extra time being in I/O for the per-batch temp files, since
> it's hard
> to see what else would be different if the data were identical in each run.
> Maybe the kernel is under memory pressure and is dropping the file data from
> in-memory disk cache. Or maybe i
On 1 July 2014 20:20, Tom Lane wrote:
> I don't plan to work on this myself, but perhaps someone with more
> motivation will want to run with these ideas.
I was planning to work on improving performance of replication apply
over the summer, mid July - Aug, so I'll add this to the list.
--
Sim
