| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
| Date: | 2014-12-23 16:02:42 |
| Message-ID: | CA+Tgmobz5PzBYvTZErv3Hxw-gERbPx=w9T4+OxwD-f73zDjpYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Dec 23, 2014 at 10:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Meh. To the extent that users look at pg_roles rather than pg_authid,
> it's going to look like another 15 boolean columns to them anyway ...
> except that now, those columns are suddenly a lot more expensive to read.
Ugh. I think that's actually a really good point. I guess I'll +1
reverting this, then.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-12-23 16:07:32 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
| Previous Message | José Luis Tallón | 2014-12-23 16:00:43 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-12-23 16:07:32 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
| Previous Message | José Luis Tallón | 2014-12-23 16:00:43 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |