[PERFORM] Optimizing timestamp queries? Inefficient Overlaps?

I have a table similar to this: CREATE TABLE event_resources ( event_resource_id serial NOT NULL, event_id integer NOT NULL, resource_id integer NOT NULL, start_date timestamptz NOT NULL, end_date timestamptz NOT NULL, CONSTRAINT event_resources_pkey PRIMARY KEY

Re: [PERFORM] Optimizing timestamp queries? Inefficient Overlaps?

Adam Rich [EMAIL PROTECTED] writes: I have a table similar to this: CREATE TABLE event_resources ( event_resource_id serial NOT NULL, event_id integer NOT NULL, resource_id integer NOT NULL, start_date timestamptz NOT NULL, end_date timestamptz NOT NULL,