| From: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Greg Williamson <gwilliamson39(at)yahoo(dot)com>, Sam Mason <sam(at)samason(dot)me(dot)uk>, Joshua Brindle <method(at)manicmethod(dot)com> |
| Subject: | Re: SE-PostgreSQL Specifications |
| Date: | 2009-08-04 23:04:20 |
| Message-ID: | 4A78BE74.8020400@ak.jp.nec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>>> * KaiGai Kohei (kaigai(at)ak(dot)jp(dot)nec(dot)com) wrote:
>>>> My concern is "access_control_" is a bit long for prefixes,
>>>> but "ac_" is too short to represent what it is doing.
>>> pg_ac_? Still shorter than 'security_', uses the pg_ prefix, which we
>>> use in a number of other places, and has 'ac' in it..
>> I don't see anything wrong with "ac_". Short is good, and there isn't
>> any other concept in the PG internals that it would conflict with.
>> If there were, "pg_ac_" would surely not help to disambiguate.
>
> Works for me.
OK, I'll go on with the "ac_" prefix.
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-08-04 23:24:45 | Re: the case for machine-readable error fields |
| Previous Message | Robert Haas | 2009-08-04 23:04:13 | Re: Filtering dictionaries support and unaccent dictionary |