You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WITH s AS (
SELECT"id"FROMpublic.taskAS t LEFT JOIN"pg_catalog"."pg_locks"AS l ON"locktype" OPERATOR(pg_catalog.=) 'userlock'AND"mode" OPERATOR(pg_catalog.=) 'AccessExclusiveLock'AND"granted"AND"objsubid" OPERATOR(pg_catalog.=) 4AND"database" OPERATOR(pg_catalog.=) 1AND"classid" OPERATOR(pg_catalog.=) ("id" OPERATOR(pg_catalog.>>) 32) AND"objid" OPERATOR(pg_catalog.=) ("id" OPERATOR(pg_catalog.<<) 32 OPERATOR(pg_catalog.>>) 32)
WHERE"state"IN ('TAKE', 'WORK') ANDl.pid IS NULL FOR UPDATE OF t skip locked
) UPDATEpublic.taskAS t SET"state"='PLAN', "start"=NULL, "stop"=NULL, "pid"=NULLFROM s WHEREt.id OPERATOR(pg_catalog.=) s.id RETURNING t.id;
PS001: Unqualified operator: '='in state IN ('TAKE', 'WORK') at line1
PS017: Unqualified object reference: t at line1
The text was updated successfully, but these errors were encountered:
You can fix the first issue by locking down your search_path like so: SET search_path TO pg_temp, pg_catalog;
Since the = is implicit there is no other way to explicitly specify the schema for the operator.
The 2nd seems to be a bug, since t is an alias and the actual table is fully schema-qualified it shouldnt complain here.
How can I resolve these warnings?
The text was updated successfully, but these errors were encountered: