| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Larry Rosenman" <lrosenman(at)pervasive(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Will Reese <wreese(at)rackspace(dot)com> |
| Subject: | Re: [GENERAL] Autovacuum Logging |
| Date: | 2006-04-29 01:54:17 |
| Message-ID: | 19021.1146275657@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> If Larry can do the work of getting details added into the stats views, I'm
> comfortable just setting all of the logging to debug1 and leaving it at that.
> I still could see the idea of having a guc for an autovacuum specific log
> control; I could see an admin who first enables autovacuum might want to log
> all its activity for some period of time; but the angle of "need to verify it
> is turned on" goes away with the stats info.
Yeah, there's a lot to be said for that point. I was about to object
that you might not have stats turned on, but if you're running autovac,
I guess you do...
So let's temporarily forget the idea of complicating autovac's logging
code, and instead see if the stats approach will solve the problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Mayrhofer | 2006-04-29 12:34:16 | Order of triggers and sequences... |
| Previous Message | Robert Treat | 2006-04-29 01:26:53 | Re: [GENERAL] Autovacuum Logging |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2006-04-29 05:14:17 | for statement, adding a STEP clause? |
| Previous Message | Robert Treat | 2006-04-29 01:26:53 | Re: [GENERAL] Autovacuum Logging |