From: pginfo <pginfo@t1.unisoftbg.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: bad join performance
Date: Tue, 19 Aug 2003 05:25:42 +0200
Message-ID: <3F4198B6.7A24F36F@t1.unisoftbg.com> (raw)
References: <3F40E9A9.12AE5D55@t1.unisoftbg.com>
<28775.1061232021@sss.pgh.pa.us>
<3F419680.B70BDA19@t1.unisoftbg.com>
<19949.1061267078@sss.pgh.pa.us>
Ok,
thanks for the help
and best regards.
ivan.
Tom Lane wrote:
> pginfo <pginfo@t1.unisoftbg.com> writes:
> > sorry for my bad.
> > My production server is 7.3.7, but the development is 7.3.1 and I ran the
> > tests on 7.3.1.
>
> > It is courios that on 7.3.1 the query is not constantly bad.
> > From time to time it is running well.
>
> Yeah, the mergejoin estimation bug doesn't bite in every case (if it
> did, we'd have found it before release ;-)). Please update to 7.3.4.
>
> regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: pginfo@t1.unisoftbg.com, tgl@sss.pgh.pa.us
Subject: Re: bad join performance
In-Reply-To: <3F4198B6.7A24F36F@t1.unisoftbg.com>
References: <3F40E9A9.12AE5D55@t1.unisoftbg.com> <28775.1061232021@sss.pgh.pa.us> <3F419680.B70BDA19@t1.unisoftbg.com> <19949.1061267078@sss.pgh.pa.us> <3F4198B6.7A24F36F@t1.unisoftbg.com>
* 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