Re: gettimeofday is at the end of its usefulness? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: gettimeofday is at the end of its usefulness?
Date
Msg-id 20160707184823.fvgp2tkrpxvjvddz@alap3.anarazel.de
Whole thread Raw
In response to Re: gettimeofday is at the end of its usefulness?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2016-07-07 14:43:31 -0400, Robert Haas wrote:
> On Tue, Jun 14, 2016 at 4:27 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> > Semi-related: someone (Robert I think) recently mentioned investigating
> > "vectorized" executor nodes, where multiple tuples would be processed in one
> > shot. If we had that presumably the explain penalty would be a moot point.
> 
> Yeah, both Andres and I are interested in that, and I think he's
> actively working on it.  It would be quite neat if this had the effect
> of reducing EXPLAIN ANALYZE's overhead to something trivial.

I am, and it does reduce the overhead. Depends on the type of plan
though. Index nestloops e.g. don't benefit on the inner side.

Andres



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: gettimeofday is at the end of its usefulness?
Next
From: Pete Stevenson
Date:
Subject: Re: MVCC overheads