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.
On 11/09/2014 10:58 AM, Kevin Wooten wrote:
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
Kevin Wooten kd...@me.com writes:
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.
Worksforme:
regression=# create table foo (f1 uuid primary key);
CREATE TABLE
regression=# explain select * from foo where f1
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
