| From: | Alvaro Herrera from 2ndQuadrant <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: roll pg_stat_statements into core |
| Date: | 2019-09-05 16:07:55 |
| Message-ID: | 20190905160755.GA6413@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Sep-02, Euler Taveira wrote:
> At least if pg_stat_statements
> was in core you could load it by default and have a GUC to turn it
> on/off without restarting the server (that was Magnus proposal and
> Andres agreed). I support this idea.
Actually this is possible without moving to part of core, too -- change
things so that putting it in shared_preload_libraries reserves the shmem
area but does not enable collection, then have a separate GUC that
enables/disables collection. A bit like archive_mode=on,
archive_command=/bin/true, which allows to change archive_command
without restarting.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2019-09-05 16:54:33 | Re: accounting for memory used for BufFile during hash joins |
| Previous Message | Tom Lane | 2019-09-05 15:53:31 | Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? |