From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unrecognized type error (postgres 9.1.4) |
Date: | 2013-04-08 14:27:22 |
Message-ID: | CANs8QJa+hCcfR0dK94NcJwXZ2ORjOxFDF0ra4FLdDYJ55tLUjw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 8, 2013 at 11:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> writes:
> > UPDATE tm32 SET a = a + 1 WHERE a > $i;
> > ERROR: unsupported type: 202886
>
> I'm betting that's coming from scalargtsel, which doesn't know anything
> about your type, but you've nominated it to be the selectivity function
> for ">" anyway.
>
> /*
> * Can't get here unless someone tries to use
> scalarltsel/scalargtsel on
> * an operator with one numeric and one non-numeric operand.
> */
> elog(ERROR, "unsupported type: %u", typid);
>
> regards, tom lane
>
Yes, I found it in the code, but I followed the example from the postgres
documentation that uses this function.
And why does it work sometimes? Why not other times?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-04-08 14:36:26 | Re: [COMMITTERS] pgsql: Get rid of USE_WIDE_UPPER_LOWER dependency in trigram constructi |
Previous Message | Tom Lane | 2013-04-08 14:25:08 | Re: Unrecognized type error (postgres 9.1.4) |