4 ms·
Take a look at this Postgres Extension: http://pghintplan.osdn.jp/pg_hint_plan.html http://pghintplan.osdn.jp/pg_hint_plan.html I am even using this with AWS R
by ganomi 5y ago
Take a look at this Postgres Extension: http://pghintplan.osdn.jp/pg_hint_plan.html http://pghintplan.osdn.jp/pg_hint_plan.html
I am even using this with AWS RDS since it comes in the set of default extensions that can be activated.
- rattray 5y agoThe pg_hint_plan is now being developed on github: https://github.com/ossc-db/pg_hint_plan https://github.com/ossc-db/pg_hint_plan I recently put up a PR for a README, you can read it here: https://github.com/ossc-db/pg_hint_plan/blob/8a00e70c387fc07ca2c3552d691031c589efd394/README.md https://github.com/ossc-db/pg_hint_plan/blob/8a00e70c387fc07...
- ollysb 5y agoThis looks very interesting. I had real difficulty where I needed both a btree and gin(pg_trgm) index on the same column. When using `like` postgres would consistently choose the btree index which resulted in performance that was something like 15secs as opposed to the 200ms or so I'd see if the gin index were used. In the end I added two separate columns, one for each index so that I could force the correct one to be used for a particular query.