On 03/18/2011 09:02 AM, Pavel Stehule wrote:
for example queries with LIMIT clause can be significantly faster with
nested loop. But you don't need to disable nested loop globally.
You can wrap your query to sql functions and disable nested loop just
for these functions.
Thank you for your help, the LIMIT example was something I was not aware of.
The problem is we are replacing an old database, and we need to
replicate certain views for external users. Minimal impact for these
users is required. Maybe it would be best to create special user
accounts for these external users and disable nested loops only for
those accounts. Otherwise we will disable nested loops when absolutely
necessary.
- Anssi
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
