Re: t_self as system column
| От | Tom Lane |
|---|---|
| Тема | Re: t_self as system column |
| Дата | |
| Msg-id | 7444.1278358014@sss.pgh.pa.us обсуждение |
| Ответ на | Re: t_self as system column (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: t_self as system column
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jul 5, 2010 at 2:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> At one time I was hoping to get rid of explicit entries in pg_attribute
>> for system columns, which would negate this concern. �I think we're
>> stuck with them now, though, because of per-column permissions.
> Because someone might want to grant per-column permissions on those
> columns? That seems like an awfully thin reason to keep all that
> bloat around. I bet the number of people who have granted per-column
> permissions on, say, cmax can be counted on one hand - possibly with
> five fingers left over.
I'd agree with that argument for the most part, but I'm not entirely
sure about oid, which has some characteristics of a user-data column.
(OTOH, maybe we could allow just oid to retain an explicit pg_attribute
entry... could be messy though.)
regards, tom lane
В списке pgsql-hackers по дате отправления: