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

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

pgsql-hackers by date

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

pgsql-jdbc by date

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

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