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

From: Thomas Burdairon <tburdairon(at)entelience(dot)com>
To: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
Cc: "Dave Cramer" <pg(at)fastcrypt(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-10 09:47:36
Message-ID: 4A78EDE1-92E9-49BA-9B67-DD1B8140ABA8@entelience.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Is there any patch available for this one?

I'm encountering troubles with some JDBC queries and I'd like to test
it before asking some help on the JDBC list.

Thanks.
Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Dunstan 2008-04-10 09:57:38 Re: Commit fest queue
Previous Message Mario Weilguni 2008-04-10 09:46:55 Re: Setting a pre-existing index as a primary key

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2008-04-10 10:44:20 Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Previous Message Toru SHIMOGAKI 2008-04-10 04:36:10 Re: Patch to add a socketTimeout property.