Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: auditing in postgresql
- From: Jeff Davis <pgsql(at)j-davis(dot)com>
- To: Merlin Moncure <mmoncure(at)gmail(dot)com>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: auditing in postgresql
- Date: Fri, 31 Aug 2007 10:08:26 -0700
- Message-id: <1188580106.6199.71.camel@dogma.ljc.laika.com> <text/plain>
On Thu, 2007-08-30 at 21:43 -0400, Merlin Moncure wrote: > Well, a SRF may be unsuitable for various reasons, but maybe views are > better. I really like views more and more lately (better than > functions as a rule, I think). > > you have some query, select yadda > create view log_yadda as > select yadda > union all select null, null, null from log_func(); > Interesting idea, I hadn't thought of that. Not perfect, but interesting. The "returns query" might help reduce the penalty of using a SRF. Maybe I'll look into that. Regards, Jeff Davis
- Follow-Ups:
- Re: auditing in postgresql
- From: Merlin Moncure
- Re: auditing in postgresql
- References:
- auditing in postgresql
- From: Jeff Davis
- Re: auditing in postgresql
- From: Merlin Moncure
- auditing in postgresql
- Prev by Date: computing and updating the size of a table with large objects
- Next by Date: Re: auditing in postgresql
- Previous by thread: Re: auditing in postgresql
- Next by thread: Re: auditing in postgresql
- Indexes: