> Chris/ Josh- > > OK-response to Chris below. Synopsis here....simply by creating a foreign > key will not create an index. On large tables I SHOULD put a non-unique > index on the foreign key (right?)
For large tables, I guess you may as well. You can be more scientific about it if you you unhash this in your postgresql.conf: stats_command_string = true stats_row_level = true stats_block_level = true Then you can just use the pg_stat views to see how many sequential scans are being run over your tables and how expensive they are, etc. Chris ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
