Re: Add min and max execute statement time in pg_stat_statement - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Add min and max execute statement time in pg_stat_statement
Date
Msg-id 18631.1390978275@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add min and max execute statement time in pg_stat_statement  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Responses Re: Add min and max execute statement time in pg_stat_statement  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Re: Add min and max execute statement time in pg_stat_statement  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp> writes:
> By the way, latest pg_stat_statement might affect performance in Windows system. 
> Because it uses fflush() system call every creating new entry in 
> pg_stat_statements, and it calls many fread() to warm file cache.

This statement doesn't seem to have much to do with the patch as
committed.  There are no fflush calls, and no notion of warming the
file cache either.  We do assume that the OS is smart enough to keep
a frequently-read file in cache ... is Windows too stupid for that?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP patch (v2) for updatable security barrier views
Next
From: "Erik Rijkers"
Date:
Subject: Re: Re: Patch: regexp_matches variant returning an array of matching positions