Re: Updates of SE-PostgreSQL 8.4devel patches (r1324)

From: KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org, simon(at)2ndQuadrant(dot)com
Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1324)
Date: 2008-12-19 16:27:20
Message-ID: 494BCB68.1060602@kaigai.gr.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark wrote:
> KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> writes:
>
>> I didn't replace the previous implementation blindly, I have a few
>> reasons that the current one is better than previous one.
>>
>> For example, if an input handler has side-effects, what is happen in
>> the following query?
>>
>> SELECT 'valid_but_new_security_label'::regseclabel;
>>
>> It looks like a read-only query, but the input handler can insert a new
>> tuple into pg_security. In addition, the newly inserted tuple may not
>> be refered any more. It is a waste of spaces.
>
> Ooh, and how would we know when to vacuum this label?

It is not necessary, because the number of security labels
are assumed enough small.

Thanks,
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2008-12-19 16:38:04 Re: SQL/MED compatible connection manager
Previous Message Peter Eisentraut 2008-12-19 16:25:20 pgsql: SQL/MED catalog manipulation facilities This doesn't do any