03.02.2017 22:16, Andres Freund:
[...]
Well, profiling postgres.exe is still beyond my capability at this time
anyway. Instead, I'll try to prepare a most simple client application
example for testing the behaviour in question so that anyone could run it
easily. (And while working on such an exam
05.02.2017 17:10, I wrote:
[...]
And yes, running Process Explorer gave some new and unexpected input.
During the period of this strange high load it claims 40% CPU is used by
interrupts (normally 0.01%) and 3% used by backend postgres.exe
(normally approx 0%). I'd guess this means some problem h
Hello,
I just stumbled about a report that has been running for a long time now and that relied on the
fact that the interval "timestamp - timestamp" always returns an interval with days,
hours, minutes. But never a "justified" interval with years, months, days and so on.
The query usees "extr
On 02/05/2017 01:21 PM, Thomas Kellerer wrote:
Hello,
I just stumbled about a report that has been running for a long time now
and that relied on the fact that the interval "timestamp - timestamp"
always returns an interval with days, hours, minutes. But never a
"justified" interval with years,
unfortunately i cannot try the restart with -R either but i ll check the
source code.
thank you all
--
View this message in context:
http://postgresql.nabble.com/pgbouncer-increase-pool-size-reload-does-not-work-tp5942273p5942711.html
Sent from the PostgreSQL - general mailing list archive at
Adrian Klaver schrieb am 05.02.2017 um 22:40:
>> I just stumbled about a report that has been running for a long time now
>> and that relied on the fact that the interval "timestamp - timestamp"
>> always returns an interval with days, hours, minutes. But never a
>> "justified" interval with years,
