st=0.00..21573.04 rows=436426
width=54) (actual time=5.523..6304.657 rows=462931 loops=1)
Filter: ((received_date >= '2004-11-01'::date) AND
(received_date <= '2004-11-30'::date))
Total runtime: 29870.437 ms
This database gets vacuumed nightly. Al
retrieve
a few hundred thousand rows from disk, faster disks might make the
biggest impact on performance.
Thanks for your help!
--
Dave Steinberg
http://www.geekisp.com/
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
This offloads the notification element
from the database, and lets you pass along any data you want to the
listeners - even the complete record.
Also this sort of thing scales well to multiple listeners. Anyway, just
a thought...
Regards,
--
Dave Steinberg
http://www.ge
l,
person_id integer not null,
primary key (image_id, person_id)
);
Similarly, for locations it'd be (image_id, location_id), and for events
(image_id, event_id). Then you can have a single image associated with
any number of people, events, or locations.
Regards,
--
Dave Steinbe
