-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved repository description? #178
Comments
I would suggest something even simpler, because we have a README that explains what this extension does:
@yamatattsu It happens that I don't have an access to that. Perhaps you could improve the description of this repository? |
Yeah, that sounds good too. 😄 |
Hi Michael-san,
@yamatattsu <https://github.com/yamatattsu> It happens that I don't have an
access to that. Perhaps you could improve the description of this
repository?
Yeah, I can improve that probably.
So I'll fix that on this weekend.
|
Hi Michael and Justin,
Extension adding support for query hint plans in PostgreSQL
I realized "query hint plans" as Michael-san proposed seems like a
typo: s/query hint plans/query hint/ ?
Even if it was typo, the word "query hint" is not popular, so I'd like
to propose the following:
Extension adding support for optimizer hints in PostgreSQL
It is good for the description because the word "optimizer hints" is
used on PostgreSQL wiki like this:
https://wiki.postgresql.org/wiki/OptimizerHintsDiscussion
What do you guys think about that?
Regards,
Tatsuro Yamada
|
The phrase structure sounds good. I'm unsure if "optimizer" is better than "query plan" hints though? If "optimizer" is more accurate, then this has my vote (for whatever that's worth). 😉 |
If the term 'optimizaer hints' is sufficiently widespread, I think it's appropriate to use it, considering that this tool doesn't always end up completely correcting plans. |
Hi Justin and Horiguti, Thanks for the comments. If it has a problem or something, let's consider a more suitable word and fix it again later. Thanks, |
I'm going to close this issue because I fixed the description, |
Cool, seems good. Thanks for getting it done. 😄 |
The existing description for this repository isn't great English:
Is it ok to suggest improvements, maybe something like this?
... or maybe use "Tell PostgreSQL ..." there instead of "Force PostgreSQL ..."
What do you reckon? 😄
The text was updated successfully, but these errors were encountered: