| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Status of autovacuum and the sporadic stats failures ? |
| Date: | 2007-02-07 19:48:49 |
| Message-ID: | 20070207194849.GF6152@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > Tom Lane wrote:
> >> It'd be interesting to try to gather stats on the length of the delay
> >> taken, but I don't see a good way to do that within the current
> >> regression-test infrastructure.
>
> > Have it log something that will appear on the postmaster log but not the
> > client log? Buildfarm members mostly post their complete postmaster
> > logs, and we could postprocess those.
>
> I've applied a patch along this line --- it'll emit LOG messages like
>
> LOG: wait_for_stats delayed 0.112799018621445 seconds
Beluga just failed:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=beluga&dt=2007-02-07%2019:30:01
The delay seems too short though:
LOG: wait_for_stats delayed 0.000748 seconds
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-07 20:04:47 | Re: Status of autovacuum and the sporadic stats failures ? |
| Previous Message | Alvaro Herrera | 2007-02-07 19:45:32 | Re: Status of autovacuum and the sporadic stats failures ? |