Re: SE-PostgreSQL Specifications - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SE-PostgreSQL Specifications
Date
Msg-id 21798.1249393273@sss.pgh.pa.us
Whole thread Raw
In response to Re: SE-PostgreSQL Specifications  (Stephen Frost <sfrost@snowman.net>)
Responses Re: SE-PostgreSQL Specifications  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * KaiGai Kohei (kaigai@ak.jp.nec.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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: doing %-expansion in plpgsql RAISE USING
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Cause pg_proc.probin to be declared as text, not bytea.