Re: Consecutive Query Executions with Increasing Execution Time

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Shijia Wei <shijiawei(at)utexas(dot)edu>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Consecutive Query Executions with Increasing Execution Time
Date: 2019-12-16 20:50:17
Message-ID: 19575.1576529417@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> Why do the first and the twentieth executions of the query have almost
> identical "buffers shared/read" numbers? That seems odd.

It's repeat execution of the same query, so that doesn't seem odd to me.

This last set of numbers suggests that there's some issue with the
parallel execution infrastructure in particular, though I don't see what
it would be. Doesn't execParallel wait for the workers to exit before
the leader finishes its query? If so, how is there any persistent state
that would interfere with a later query?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Nicolas Charles 2019-12-16 22:08:52 Re: Consecutive Query Executions with Increasing Execution Time
Previous Message Peter Geoghegan 2019-12-16 20:39:10 Re: Consecutive Query Executions with Increasing Execution Time