From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
Date: | 2014-12-23 15:36:41 |
Message-ID: | 31639.1419349001@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> Again, I suppose I should have objected earlier, but I really seriously
>> doubt that this is a good idea.
> Ugh. I thought we had a consensus that this was the accepted way
> forward; that's my reading of the old thread,
> http://www.postgresql.org/message-id/flat/20141016133218(dot)GW28859(at)tamriel(dot)snowman(dot)net#20141016133218(dot)GW28859@tamriel.snowman.net
I was aware that we were thinking of introducing a bunch more role
attributes, but I'm wondering what's the rationale for assuming that
(a) they'll all be booleans, and (b) there will never, ever, be more
than 64 of them. The argument that lots of boolean columns won't
scale nicely doesn't seem to lead to the conclusion that a fixed-size
bitmap is better.
I'd have gone with just adding more bool columns as needed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-12-23 15:40:15 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
Previous Message | Stephen Frost | 2014-12-23 15:34:47 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-12-23 15:40:15 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |
Previous Message | Stephen Frost | 2014-12-23 15:34:47 | Re: [COMMITTERS] pgsql: Use a bitmask to represent role attributes |