> On Jan 25, 2025, at 2:42 PM, frits.hoogl...@gmail.com wrote:
>
> One thing I found is that because certain statistics are provided after a
> query has run, measuring them in a fine grained way shows a peak for
> something that in reality is taking place over a period of time.
+1
I have al
Your settings are interesting, I'm curious what the goal is for this
particular hammerdb exercise.
A few comments inline
On 10/12/21 00:35, Ashkil Dighin wrote:
>
> Postgres.conf used in Baremetal
>
> maintenance_work_mem = 512MB
only a half GB memory for a
On Oct 7, 2021, at 19:38, Bruce Momjian wrote:
>
> On Thu, Oct 7, 2021 at 07:15:39PM -0700, Jeremy Schneider wrote:
>> PostgreSQL added wait events starting in 9.6 and the last thing that's
>> missing is an integrated way to trace or log them. A simple starting
>
On 10/5/21 13:24, Peter Geoghegan wrote:
> On Fri, Oct 1, 2021 at 1:06 PM Jeff Holt wrote:
>> Now looking closely at postgreSQL, I see an opportunity to more quickly
>> implement Oracle's current feature list.
>>
>> I've come to this point because I see many roadblocks for users who want to
>> s
pg_hint_plan extension might be able to force a plan.
Also, I don’t know if perf probes & perf record/script could be useful for
creating a log of all the calls to do memory allocation along with the unwound
call stacks? Then analyzing that file? At least this can be done for a single
process,
On 3/14/19 00:29, Stephan Schmidt wrote:
> i’m currently working on a high Performance Database and want to make
> sure that whenever there are slow queries during regular operations i’ve
> got all Information about the query in my logs. So auto_explain come to
> mind, but the documentation explici
