From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Jeff Davis" <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: auditing in postgresql |
Date: | 2007-08-31 19:51:53 |
Message-ID: | b42b73150708311251w4f55e591p40f6153b5ed3ac38@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/31/07, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Fri, 2007-08-31 at 13:51 -0400, Merlin Moncure wrote:
> > > how about this:
> > > create view log_yadda sa
> > > select yadda where (select func());
> > >
> > > the parens around the function call force it to be evaluated as a scalar.
> >
> > if you declare func() immutable, you can (maybe) remove the parens
> > because the planner folds the call to a constant. This is faster in
> > some cases because
> >
>
> I like this approach. I'm a little concerned about PREPARE, however. I
> think that might only execute the function once and then not on
> subsequent calls, which would then not be audited.
At present, immutable functions are only treated as constants during a
query, which is what we want (no problems with prepare). I am a
little bit concered about interactions with queries wrapping the
view...you'll just have to try and see.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-31 20:30:00 | Re: auditing in postgresql |
Previous Message | Tom Lane | 2007-08-31 19:11:29 | Re: [GENERAL] Undetected corruption of table files |