Re: [PATCH] Largeobject access controls

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Largeobject access controls
Date: 2009-09-22 17:53:22
Message-ID: 603c8f070909221053q7cabd1c2tb462aabee40eb705@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 22, 2009 at 1:29 PM, Jaime Casanova
<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> have anyone better ideas about the name? if not, then go with
> pg_largeobject_meta

I don't think there's anything wrong with calling it metadata. That
seems to leave the door open to future things we might want to do,
without restricting it to security-related settings or whatever. But
I don't see any reason to abbreviate it either - I'd go with
pg_largeobject_metadata rather than just pg_largeobject_meta.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-09-22 17:56:32 Re: Anonymous code blocks vs CREATE LANGUAGE
Previous Message Robert Haas 2009-09-22 17:50:45 Re: Anonymous code blocks vs CREATE LANGUAGE