ake use of it a few
times and have had no problems.
-salman
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
bol");
CREATE INDEX idx_fk_lockerevents_iduser_users_id
ON "LockerEvents"
USING btree
("IDUser");
CREATE UNIQUE INDEX idx_pk_lockerevents_id
ON "LockerEvents"
USING btree
("ID");
If I do the query :
SELECT * FROM "LockerEvents" LIMIT
aintenance windows (we're a 24/7 shop) and do clustering and
other tasks on our DB to reclaim space, etc.
-salman
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
tch value.
I'm assuming that idx_tup_read would probably be the best choice, but
want to get other opinions before proceeding.
Can anyone point me to docs which explain this better?
-salman
---(end of broadcast)---
TIP 9: In versions below 8