From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Magnus Hagander <magnus(at)hagander(dot)net>, sk(at)zsrv(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Dave Page <dpage(at)pgadmin(dot)org> |
Subject: | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
Date: | 2018-11-22 14:18:23 |
Message-ID: | CAA4eK1L+7rJTdkpQDkZmgj8PGWS_=m-RKfZ7-9-1U7b0z4uBbw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 22, 2018 at 7:02 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> On 2018-Nov-20, Haribabu Kommi wrote:
>
> > > > 4. Single API with -1 as invalid value, treat NULL as no matching. (Only
> > > problem
> > > > with this approach is till now -1 is also a valid queryid, but setting
> > > -1 as queryid
> > > > needs to be avoided.
> > >
> > > Hmm, can we use 0 as default value without any such caveat?
> >
> > Yes, with strict and 0 as default value can work.
> > If there is no problem, I can go ahead with the above changes?
>
> I'm not sure I understand this proposal. Does this mean that passing -1
> as databaseid / userid would match all databases/users, and passing 0 as
> queryid would match all queries?
>
No, for userid/databaseid also it will be 0 (aka InvalidOid).
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2018-11-22 14:21:15 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
Previous Message | Patrick Francelle | 2018-11-22 14:16:11 | Constraint documentation |