From: Bruce Momjian <bruce@momjian.us>
To: Mel Llaguno <mllaguno@coverity.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Performance bug in prepared statement binding in 9.2?
Date: Tue, 10 Sep 2013 07:50:18 -0400
Message-ID: <20130910115018.GD32160@momjian.us> (raw)
In-Reply-To: <E1FB7FBAE29E634FA58D6CC0D59F288B3412B59F@CH1PRD0511MB442.namprd05.prod.outlook.com>
References: <E1FB7FBAE29E634FA58D6CC0D59F288B3412B59F@CH1PRD0511MB442.namprd05.prod.outlook.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On Tue, Sep 10, 2013 at 05:43:16AM +0000, Mel Llaguno wrote:
> Bruce,
>
> First of all, I'd like to thank you for taking some interest in this
> issue. We'd love to migrate to the latest PG version, but this issue
> is currently preventing us from doing so.
>
> Regardless of the DB used (base application schema _or_ restored DB
> with additional app data + base application schema), seed information
> is present in all tests. I guess my question is this - why would
> having existing data change the bind behavior at all? Is it possible
> that the way indexes are created has changed between 8.4 -> 9.x?
I don't know as you have not shown us exactly what is slower between
versions --- you only said the bug appears or not in certain
circumstances.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruce@momjian.us, mllaguno@coverity.com
Subject: Re: Performance bug in prepared statement binding in 9.2?
In-Reply-To: <20130910115018.GD32160@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox