From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Operator is not unique |
Date: | 2019-09-30 14:39:33 |
Message-ID: | 257b0805-ed19-6f64-ece8-112ae936dbff@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/30/19 7:28 AM, PegoraroF10 wrote:
> your select returns no records but if I use
> WHERE p.proname ~ 'day_inc'
> instead of
> WHERE p.proname OPERATOR(pg_catalog.~) '^(pg_catalog.day_inc)$'
Yeah I was not paying attention to what it was really looking for, the
function name.
The list of extensions that you sent earlier are fairly common. I would
not expect them to be contributing to the below otherwise there would
have been more reports of what you are seeing.
From the name of the functions and function arguments they look like
something that is working with dates.
Does that bring anything to mind?
Do you have code you can grep for use of the functions?
>
>
> Schema
> Name
> Result data type
> Argument data types
> Type
>
>
> pg_catalog
> day_inc
> anyelement
> adate anyelement, ndays numeric
> func
>
>
> pg_catalog
> day_inc
> anyelement
> ndays numeric, adate anyelement
> func
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-09-30 14:54:15 | Re: Operator is not unique |
Previous Message | PegoraroF10 | 2019-09-30 14:28:51 | Re: Operator is not unique |