| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | "Hogan, James F(dot) Jr(dot)" <JHogan(at)seton(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, josh(at)agliodbs(dot)com, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: audit table containing Select statements submitted |
| Date: | 2006-05-15 15:42:13 |
| Message-ID: | 20060515154213.GK26212@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
How do you hope to avoid this overhead when you're looking to track
information on every single SELECT statement? Or were you looking to
only log access to some specific tables?
On Mon, May 15, 2006 at 09:38:54AM -0500, Hogan, James F. Jr. wrote:
> Thank you all for the effort you put into response.
>
> The biggest thing I want to avoid isn't so much having to parse through
> the log files but to avoid turning on such extensive logging altogether.
>
> I am not sure what kind of additional load logging to this extent may
> add.
>
> Looks like I am not going to have much in the way of alternative.
>
> Maybe some day.
>
> Good news is that most access is via Web Interface and I capture most
> activity that way.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-15 15:43:08 | Re: Creating a Pseudocolumn |
| Previous Message | Bruce Momjian | 2006-05-15 15:39:41 | Re: Compiling on 8.1.3 on Openserver 5.05 |