Re: Performance bug in prepared statement binding in 9.2?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance bug in prepared statement binding in 9.2?
Date: 2013-09-12 02:03:21
Message-ID: 523120E9.6020300@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


> The explanation is in
> http://archives.postgresql.org/message-id/20130910132133.GJ1024477%40alap2.anarazel.de
>
> The referenced commit introduced a planner feature. Funnily you seem to
> have been the trigger for it's introduction ;)

Oh, crap, the "off the end of the index" optimization?

It's the story of our lives: we can't optimize anything without
deoptimizing something else. Dammit.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Roberto Grandi 2013-09-12 06:14:11 Re: COPY TO and VACUUM
Previous Message Andres Freund 2013-09-11 21:12:53 Re: Performance bug in prepared statement binding in 9.2?