From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig James <cjames(at)emolecules(dot)com> |
Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Stefan Keller <sfkeller(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Getting query plan alternatives from query planner? |
Date: | 2014-03-21 14:06:51 |
Message-ID: | 15381.1395410811@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Craig James <cjames(at)emolecules(dot)com> writes:
> There have been many discussions about adding hints to Postgres over the
> years. All have been firmly rejected by the Postgres developers, with
> well-argued reasons. Search the archives to learn more about this topic.
To clarify: there are good reasons not to like what Oracle calls hints.
On the other hand, the concept of hints that tell the planner what
selectivity or rowcount to expect (as opposed to trying to control the
plan directly) has met with generally more positive reviews. There's
no specific design yet, and certainly no implementation roadmap, but
I'd not be surprised if we get something like that a few years down
the road.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Smet | 2014-03-21 14:49:16 | Connection pooling - Number of connections |
Previous Message | Craig James | 2014-03-21 13:34:55 | Re: Getting query plan alternatives from query planner? |