From: | jian he <jian(dot)universality(at)gmail(dot)com> |
---|---|
To: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | confused by int2vector typdelim |
Date: | 2023-05-24 07:56:51 |
Message-ID: | CACJufxFViGB-Y=fVRgb7mb8DJe4Oy09uxzVACpp18-AcM2zsSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hi.
select
pt.typtype
, pt.typcategory
, pt.typdelim
, pt.typelem
, pt1.typname as elem_type
,pt.typsubscript
,pt.typname
from pg_type pt join pg_type pt1 on pt.typelem = pt1.oid
where pt.typname = 'int2vector';
returns
typtype | typcategory | typdelim | typelem | elem_type | typsubscript
| typname
---------+-------------+---------+----------+-----------+-------------------------+------------
b | A | , | 21 | int2 |
array_subscript_handler | int2vector
(1 row)
from manual:
> typdelim char
> Character that separates two values of this type when parsing array input.
> Note that the delimiter is associated with the array element data type, not
> the array data type.
should I expect the typdelim be a white space? Since '1 2'::int2vector
works, '1,2'::int2vector does not work.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-05-24 14:09:58 | Re: confused by int2vector typdelim |
Previous Message | vignesh C | 2023-05-24 05:38:56 | Re: Support logical replication of DDLs |