From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Change Ownership Permission Checks |
Date: | 2005-07-15 19:45:01 |
Message-ID: | 18344.1121456701@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> When writing this patch it occurred to me that we nuke our
> member-of-role cache for one-off lookups on occation. I don't
> particularly like that, especially when we *know* it's a one-off lookup,
Yeah. What I had been thinking about is that maybe it shouldn't be just
a one-element cache. At the moment though we have no performance data
to justify complicating matters (heck, not even any to prove we need a
cache at all...) It'd be smart to try to profile some realistic cases
before spending any time coding.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2005-07-15 20:36:07 | Re: multibyte regression tests |
Previous Message | Stephen Frost | 2005-07-15 19:10:31 | Re: Change Ownership Permission Checks |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2005-07-15 20:04:02 | [patch 0/3] last large update to pgcrypto |
Previous Message | Stephen Frost | 2005-07-15 19:10:31 | Re: Change Ownership Permission Checks |