Re: mapping object names to role IDs - Mailing list pgsql-hackers

From Robert Haas
Subject Re: mapping object names to role IDs
Date
Msg-id AANLkTildtHmjNg8njhmtKDI1hui4JvlnjPsrmQJJg6lI@mail.gmail.com
Whole thread Raw
In response to Re: mapping object names to role IDs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: mapping object names to role IDs
List pgsql-hackers
On Wed, May 26, 2010 at 9:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This is nonsense

You can assert that, but I don't agree.  We certainly have places
(comment.c being the obvious example) where we need to look up a name
and map it to an OID without doing anything else, and actually I
believe there are useful ways to refactor the code that might lead to
more of this.  Anyway, I think the code maintenance argument ought to
carry a lot more weight than whether one or two small files get
rebuilt for dependencies slightly more often.  lsyscache.c might have
no conceptual consistency but it's extremely useful, and there are
plenty of other examples of where we've put code for different object
types into a single file to simplify maintenance and reduce code
complexity (e.g. copyfuncs, equalfuncs, outfuncs, etc.).

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Exposing the Xact commit order to the user
Next
From: Garick Hamlin
Date:
Subject: Re: libpq should not be using SSL_CTX_set_client_cert_cb