Re: [HACKERS] Undefined psql variables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] Undefined psql variables
Date
Msg-id alpine.DEB.2.20.1701232152080.31421@lancre
Whole thread Raw
In response to Re: [HACKERS] Undefined psql variables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Back in the day, PG allowed ":" as a generic operator name, making
> this even worse; but I think the only remaining SQL syntax that could
> include a colon is array slicing.

Ok, so the behavior of replacing ":unknown" by same cannot be changed.

Some fun:
  \set 1 1  SELECT ('{1,2,3,4,5,6,7,8,9,10,11,12}'::INT[])[1:1];  -- yields 11

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] Allowing nonzero return codes from \quit
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan