From: | Bob Lunney <bob_lunney(at)yahoo(dot)com> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Really really slow select count(*) |
Date: | 2011-02-16 19:20:27 |
Message-ID: | 924581.28987.qm@web39707.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Ross,
Way off topic now, but from my time programming electrical meters I can tell you pulling the meter from its socket is potentially an extremely dangerous thing to do. If there is a load across the meter's poles the spark that results on disconnect could kill the puller instantly. (You don't want to know what happens if the person isn't killed.)
I don't know what property your admin type is trying to protect, but I'm inclined to let it burn and live to work through the insurance collection process.
Oh, and +1 for timed escalation of a shutdown.
Bob Lunney
--- On Wed, 2/16/11, Ross J. Reedstrom <reedstrm(at)rice(dot)edu> wrote:
> From: Ross J. Reedstrom <reedstrm(at)rice(dot)edu>
> Subject: Re: [PERFORM] Really really slow select count(*)
<<big snip>>
>
> Following you off topic, I know of one admin type who has
> stated "I don't
> care what sort of fine the power company wants to give me,
> if my
> property's on fire, I'm going to pull the meter, in order
> to hand it to
> the first responder, rather than have them sit there
> waiting for the
> power tech to arrive while my house burns."
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-02-16 19:22:26 | Re: high user cpu, massive SELECTs, no io waiting problem |
Previous Message | Cédric Villemain | 2011-02-16 17:58:23 | Re: high user cpu, massive SELECTs, no io waiting problem |