Hi Robert,
"There is no significant disk activity (read 0), one CPU is pegged, and
that process is consuming 218M Resident memory, 168M Shared (10% available
memory total). All reasonable, except for the fact it doesn't come back..."
Just to let you know, I've observed the identical phenomeno
When grilled further on (Tue, 28 Sep 2004 11:04:23 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > Normally, this query takes from 5 minutes to 2 hours to run. On this
> > update, it's been running for more than 10 hours.
>
> > ...
> > ->
When grilled further on (Tue, 28 Sep 2004 21:41:50 -0500),
Kevin Barnard <[EMAIL PROTECTED]> confessed:
> On Tue, 28 Sep 2004 20:21:40 -0600, Robert Creager
> <[EMAIL PROTECTED]> wrote:
> >
> > The trigger keeps another table (catalog) up to date with the information
> > from the obs_v and obs_i
On Tue, 28 Sep 2004 20:21:40 -0600, Robert Creager
<[EMAIL PROTECTED]> wrote:
>
> The trigger keeps another table (catalog) up to date with the information from the
> obs_v and obs_i tables. There are no direct insert/update/delete's on the catalog
> table, only though the trigger.
>
It's pos
When grilled further on (Tue, 28 Sep 2004 16:55:13 +0200),
Gaetano Mendola <[EMAIL PROTECTED]> confessed:
> Robert Creager wrote:
> > Help?
> >
> > Normally, this query takes from 5 minutes to 2 hours to run. On this
> > update, it's been running for more than 10 hours.
> >
> > Can it be helped
When grilled further on (Tue, 28 Sep 2004 09:28:47 -0500),
Kevin Barnard <[EMAIL PROTECTED]> confessed:
> What does observations_trigger do?
>
The trigger keeps another table (catalog) up to date with the information from the
obs_v and obs_i tables. There are no direct insert/update/delete's o
Robert Creager wrote:
Help?
Normally, this query takes from 5 minutes to 2 hours to run. On this update, it's
been running for more than 10 hours.
Can it be helped?
When I see this usually means that tables are full of
dead rows. Did you vacuum you DB. Which version are you
using ?
Regards
Gaeta
Robert Creager <[EMAIL PROTECTED]> writes:
> Normally, this query takes from 5 minutes to 2 hours to run. On this update, it's
> been running for more than 10 hours.
> ...
> -> Nested Loop (cost=250.69..129094.19 rows=77211 width=59)
> -> Hash Join (cost=250.69..307.34
What does observations_trigger do?
On Tue, 28 Sep 2004 08:19:57 -0600, Robert Creager
<[EMAIL PROTECTED]> wrote:
>
> Help?
>
> Normally, this query takes from 5 minutes to 2 hours to run. On this update, it's
> been running for more than 10 hours.
>
> Can it be helped?
>
> UPDATE obs_v
> SET m
