| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | FPW stats? |
| Date: | 2018-05-02 10:22:34 |
| Message-ID: | CA+q6zcXJt2GJGQCYiei3sjSeuxO5D1TJcPS6uD9MQ8=f0KuSwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Recently I've heard people complaining that Postgres doesn't expose any
statistics about how many full page writes happened during some time frame.
Indeed, I couldn't find any easy way to do so, and judging from my
understanding of xloginsert.c it actually can be done per database with the
attached poc patch.
I guess it can be implemented in a more effective and optimized way, but with
what I have right now first naive pgbench tests show that slowdown is about 3%.
Before I'll dig into it more, it would be nice to hear your opinion about this
idea - does it make sense to have something like this?
| Attachment | Content-Type | Size |
|---|---|---|
| fpw_stat.patch | text/x-patch | 10.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2018-05-02 10:55:58 | Re: Is a modern build system acceptable for older platforms |
| Previous Message | Amit Langote | 2018-05-02 08:07:07 | Re: Should we add GUCs to allow partition pruning to be disabled? |