Skip site navigation (1) Skip section navigation (2)

Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work

From: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Stephen Frost" <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Date: 2008-04-01 05:51:11
Message-ID: 1d4e0c10803312251n1e7e1e70gdf70d2caf559517@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
On Tue, Apr 1, 2008 at 7:35 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>  Well, it's not like we have never before changed internal APIs in a
>  minor update.  (There have been security-related cases where we gave
>  *zero* notice of such changes.)  Nor am I willing to surrender the
>  option to do so again.  If there's somebody out there with a real
>  problem with this change, they need to speak up.

+1 to fix it ASAP. A lot of people usually wait for 8.x.1 before
considering a migration and people are usually quite cautious with the
8.3 migration because of all the cast errors in the existing app.

Another question is how we can be sure it doesn't happen again. The
easiest way to test this is probably to have a JDBC test testing this
exact feature in the future benchfarm. Any comment?

-- 
Guillaume

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-04-01 06:06:36
Subject: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Previous:From: Tom LaneDate: 2008-04-01 05:35:24
Subject: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work

pgsql-jdbc by date

Next:From: Tom LaneDate: 2008-04-01 06:06:36
Subject: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Previous:From: Tom LaneDate: 2008-04-01 05:35:24
Subject: Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group