Re: Deferring some AtStart* allocations?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Deferring some AtStart* allocations?
Date: 2014-10-09 12:18:18
Message-ID: CA+TgmoYe3a3L62O_HSuA2c3q7AAWJDejj-cmDaO2V54n+Q_+MQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 9, 2014 at 5:34 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Interesting - in my local profile AtStart_Inval() is more pronounced
> than AfterTriggerBeginQuery(). I've quickly and in a ugly fashion hacked
> AtStart_Inval() out of readonly queries ontop of your patch. Together
> that yields a ~3.5% performance improvement in my trivial 'SELECT * FROM
> tbl WHER pkey = xxx' testcase.

Whoa. Now that's clearly significant. You didn't attach the patch;
was that inadvertent, or was it too ugly for that?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-10-09 12:20:38 Re: Deferring some AtStart* allocations?
Previous Message Andres Freund 2014-10-09 11:26:32 Re: Escaping from blocked send() reprised.