| From: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | doc: minor update for description of "pg_roles" view |
| Date: | 2019-07-10 05:35:56 |
| Message-ID: | b6ec6167-5dd5-6347-ac1d-1fd49382019f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
Here:
https://www.postgresql.org/docs/12/view-pg-roles.html
we state:
"This view explicitly exposes the OID column of the underlying table,
since that is needed to do joins to other catalogs."
I think it's superfluous to mention this now OIDs are exposed by default;
attached patch (for REL_12_STABLE and HEAD) simply removes this sentence.
Regards
Ian Barwick
--
Ian Barwick https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| view-pg_roles.v1.patch | text/x-patch | 566 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2019-07-10 05:43:26 | Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof? |
| Previous Message | Binguo Bao | 2019-07-10 05:35:25 | Re: Optimize partial TOAST decompression |