News for hackers. Stuff that matters.
Re:Why PostgreSQL doesn't have query hints by chubs on Saturday February 05, 2011 @02:21AM (#2182673)
You can take NOLOCK out of my cold, dead, hands! That one is a lifesaver for reading from terabyte-sized OLTP tables with 100/sec inserts...

I really like what the guy is saying in the article. However, it's the perennial idealism vs pragmatism argument. And, i'll put my hand up for pragmatism: I've needed hints in the past, because like everything else in this world, query planners simply aren't perfect.

Re:Why PostgreSQL doesn't have query hints by Ingaz on Saturday February 05, 2011 @03:19AM (#2182732)
In SQLServer in general it's better to write one time SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED, than write hint NOLOCK agains each table.

Result is the same.

This is not a hint for planner. You can write it for PostgreSQL also (I mean SET TRANSACTION).