From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | holdenru(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16055: pgAdmin 4 - ERROR: operator does not exist: - oid |
Date: | 2019-10-14 23:30:08 |
Message-ID: | 1178.1571095808@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> It works OK with pgAdmin 3.
> ERROR: operator does not exist: - oid
> LINE 4: WHERE attrelid=-2016150721::oid
> ^
> HINT: No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
This is a bug in whatever generated that query (if it was pgAdmin 4,
you should complain on the pgadmin lists). Probably, it printed an
OID value as a signed integer when it should have printed it as an
unsigned integer. That's an easy mistake that doesn't show up
until your database gets past 2^31 OIDs consumed :-(.
The server error message is correct as far as it goes: there's no minus
operator for the OID type. Since OID is unsigned, it wouldn't make
a lot of sense to have one.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-10-15 00:18:17 | Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 |
Previous Message | David G. Johnston | 2019-10-14 19:53:12 | Re: BUG #16056: Actually PGADMIN4 |