| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Use of '&' as table prefix in query |
| Date: | 2021-07-12 18:02:31 |
| Message-ID: | alpine.LNX.2.20.2107121101020.7804@salmo.appl-ecosys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 12 Jul 2021, Adrian Klaver wrote:
> You should also follow Tom's suggestion and do:
> \do+ &
> in psql.
It's the bitwise 'and':
# \do+ &
List of operators
Schema | Name | Left arg type | Right arg type | Result type | Function | Description
------------+------+---------------+----------------+-------------+--------------+-------------
pg_catalog | & | bigint | bigint | bigint | int8and | bitwise and
pg_catalog | & | bit | bit | bit | bitand | bitwise and
pg_catalog | & | inet | inet | inet | inetand | bitwise and
pg_catalog | & | integer | integer | integer | int4and | bitwise and
pg_catalog | & | macaddr | macaddr | macaddr | macaddr_and | bitwise and
pg_catalog | & | macaddr8 | macaddr8 | macaddr8 | macaddr8_and | bitwise and
pg_catalog | & | smallint | smallint | smallint | int2and | bitwise and
(7 rows)
which doesn't seem appropriate in this context.
Thanks,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2021-07-12 18:04:41 | Re: Use of '&' as table prefix in query |
| Previous Message | Rob Sargent | 2021-07-12 17:51:07 | Re: Use of '&' as table prefix in query |