On Wed, May 28, 2014 at 6:51 PM, Peter Geoghegan <p...@heroku.com> wrote: > Have you thought about things like specialized prefetching for nested > loop joins?
Currently, such a thing would need some non-trivial changes to the execution nodes, I believe. For nestloop, correct me if I'm wrong, but index scan nodes don't have visibility of the next tuple to be searched for. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
