https://github.com/ossc-db/pg_hint_plan Skip to content Toggle navigation Sign in * Product + Actions Automate any workflow + Packages Host and manage packages + Security Find and fix vulnerabilities + Codespaces Instant dev environments + Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code Explore + All features + Documentation + GitHub Skills + Blog * Solutions For + Enterprise + Teams + Startups + Education By Solution + CI/CD & Automation + DevOps + DevSecOps Resources + Learning Pathways + White papers, Ebooks, Webinars + Customer Stories + Partners * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles Repositories + Topics + Trending + Collections * Pricing Search or jump to... Search code, repositories, users, issues, pull requests... Search [ ] Clear Search syntax tips Provide feedback We read every piece of feedback, and take your input very seriously. [ ] [ ] Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Name [ ] Query [ ] To see all available qualifiers, see our documentation. Cancel Create saved search Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} ossc-db / pg_hint_plan Public * Notifications * Fork 95 * Star 544 * Give PostgreSQL ability to manually force some decisions in execution plans. 544 stars 95 forks Branches Tags Activity Star Notifications * Code * Issues 16 * Pull requests 0 * Actions * Projects 0 * Wiki * Security * Insights Additional navigation options * Code * Issues * Pull requests * Actions * Projects * Wiki * Security * Insights ossc-db/pg_hint_plan This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. master BranchesTags Go to file Code Folders and files Last Last Name Name commit commit message date Latest commit History 748 Commits SPECS SPECS data data docs docs expected expected sql sql .gitattributes .gitattributes .gitignore .gitignore COPYRIGHT COPYRIGHT COPYRIGHT.postgresql COPYRIGHT.postgresql META.json META.json Makefile Makefile README.md README.md core.c core.c make_join_rel.c make_join_rel.c normalize_query.h normalize_query.h pg_hint_plan--1.3.0--1.3.1.sql pg_hint_plan--1.3.0--1.3.1.sql pg_hint_plan--1.3.0.sql pg_hint_plan--1.3.0.sql pg_hint_plan--1.3.1--1.3.2.sql pg_hint_plan--1.3.1--1.3.2.sql pg_hint_plan--1.3.2--1.3.3.sql pg_hint_plan--1.3.2--1.3.3.sql pg_hint_plan--1.3.3--1.3.4.sql pg_hint_plan--1.3.3--1.3.4.sql pg_hint_plan--1.3.4--1.3.5.sql pg_hint_plan--1.3.4--1.3.5.sql pg_hint_plan--1.3.5--1.3.6.sql pg_hint_plan--1.3.5--1.3.6.sql pg_hint_plan--1.3.6--1.3.7.sql pg_hint_plan--1.3.6--1.3.7.sql pg_hint_plan--1.3.7--1.3.8.sql pg_hint_plan--1.3.7--1.3.8.sql pg_hint_plan--1.3.8--1.3.9.sql pg_hint_plan--1.3.8--1.3.9.sql pg_hint_plan--1.3.9--1.4.sql pg_hint_plan--1.3.9--1.4.sql pg_hint_plan--1.4--1.4.1.sql pg_hint_plan--1.4--1.4.1.sql pg_hint_plan--1.4.1--1.4.2.sql pg_hint_plan--1.4.1--1.4.2.sql pg_hint_plan--1.4.2--1.5.sql pg_hint_plan--1.4.2--1.5.sql pg_hint_plan--1.5--1.5.1.sql pg_hint_plan--1.5--1.5.1.sql pg_hint_plan--1.5.1--1.6.0.sql pg_hint_plan--1.5.1--1.6.0.sql pg_hint_plan--1.6.0--1.7.0.sql pg_hint_plan--1.6.0--1.7.0.sql pg_hint_plan.c pg_hint_plan.c pg_hint_plan.control pg_hint_plan.control pg_stat_statements.c pg_stat_statements.c query_scan.h query_scan.h query_scan.l query_scan.l query_scan_int.h query_scan_int.h update_copied_funcs.pl update_copied_funcs.pl View all files Repository files navigation * README * License pg_hint_plan 1.7 pg_hint_plan makes it possible to tweak PostgreSQL execution plans using so-called "hints" in SQL comments, like /*+ SeqScan(a) */. PostgreSQL uses a cost-based optimizer, that uses data statistics, not static rules. The planner (optimizer) estimates costs of each possible execution plans for a SQL statement, then executes the plan with the lowest cost. The planner does its best to select the best execution plan, but it is far from perfect, since it may not count some data properties, like correlation between columns. For more details, please see the various documentations available in the docs/ directory: 1. Description 2. The hint table 3. Installation 4. Unistallation 5. Details in hinting 6. Errors 7. Functional limitations 8. Requirements 9. Hints list --------------------------------------------------------------------- Copyright (c) 2012-2023, NIPPON TELEGRAPH AND TELEPHONE CORPORATION About Give PostgreSQL ability to manually force some decisions in execution plans. Resources Readme Activity Custom properties Stars 544 stars Watchers 29 watching Forks 95 forks Report repository Releases 13 pg_hint_plan16 1.6.0 is released Latest Sep 13, 2023 + 12 releases Packages 0 No packages published Contributors 20 * @metrohasegawa * @hanada * @michaelpq * @horiguti * @rjuju * @yamatattsu * @za-arthur * @dependabot[bot] * @LittleWuCoding * @tideri * @Anisimov-ds * @xzilla * @felixge * @MasaoFujii + 6 contributors Languages * C 68.8% * PLpgSQL 16.9% * Lex 10.3% * Perl 3.1% * Other 0.9% Footer (c) 2024 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact * Manage cookies * Do not share my personal information You can't perform that action at this time.