I am assuming I am crazy and missing something completely obvious but I cannot
get postgres (9.3.5) to use an index on a UUID, ever.
The main table has a natural composite key (2 uuids and a timestamp) with which
it always uses the timestamp as the index condition and filters on the UUIDs.
This affirmation that it indeed does work set me straight. I inadvertently made
a previously immutable UUID function volatile; it was providing the UUIDs in
the query.
On Nov 9, 2014, at 2:12 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Wooten kd...@me.com writes:
I am assuming I am crazy
Regardless of type used… the driver and server should agree on the results.
On Jan 3, 2014, at 6:06 PM, Scott Marlowe scott.marl...@gmail.com wrote:
On Fri, Jan 3, 2014 at 5:55 PM, Adrian Klaver adrian.kla...@gmail.com wrote:
Only thing I can think of is the JDBC driver and Postgres have a
On Nov 19, 2013, at 6:33 PM, Kevin Wooten kd...@me.com wrote:
My apologies for posting what is almost certainly somewhat of a repeat
question but I have searched and attempted everything I can think of and
cannot figure it out myself.
The basic question is… Is it possible to get
and knowledge of
others ;)
On 11/22/2013 2:27 PM, Kevin Wooten wrote:
On Nov 19, 2013, at 6:33 PM, Kevin Wooten kd...@me.com wrote:
My apologies for posting what is almost certainly somewhat of a repeat
question but I have searched and attempted everything I can think of and
cannot figure it out
My apologies for posting what is almost certainly somewhat of a repeat question
but I have searched and attempted everything I can think of and cannot figure
it out myself.
The basic question is… Is it possible to get a scrollable cursor that, within a
transaction, can insert/update/delete
