| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planning counters in pg_stat_statements (using pgss_store) |
| Date: | 2019-02-13 07:53:44 |
| Message-ID: | 9846851550044424@iva8-60b043ae986f.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
> I think it is related to https://commitfest.postgresql.org/16/1373/
> but I don't know how to link it with.
You can just add new entry in open commitfest and then attach previous thread. This is usual way for pick up old patches. For example, as i did here: https://commitfest.postgresql.org/20/1711/
> Yes, there are many things to improve, but before to go deeper,
> I would like to know if that way to do it (with 3 access to pgss hash)
> has a chance to get consensus ?
I can not say something here, i am not experienced contributor here.
Can you post some performance test results with slowdown comparison between master branch and proposed patch?
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2019-02-13 08:21:33 | Re: Protect syscache from bloating with negative cache entries |
| Previous Message | Haribabu Kommi | 2019-02-13 07:42:36 | Re: pg_basebackup ignores the existing data directory permissions |