| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add more information_schema columns |
| Date: | 2018-02-06 20:16:59 |
| Message-ID: | CA+TgmoY+Zt6q5Jj4o=yZ6P_-Sz00MOEysk=zULYtqSa8nKdoXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 6, 2018 at 2:15 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Better to use parenthesis for (t.tgtype & 1 & 66) perhaps? You may want
> to comment that this is to filter per row-statement first, and then with
> after/before/instead of, which are what the 1 and the 66 are for.
What possible point can there be to such an expression? It's always 0.
rhaas=# select distinct tgtype::smallint & 1 & 66 from
generate_series(-32768,32767) tgtype;
?column?
----------
0
(1 row)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-02-06 20:17:50 | Re: Add PGDLLIMPORT to enable_hashagg |
| Previous Message | Robert Haas | 2018-02-06 20:11:12 | Re: RelOptInfo -> Relation |