To pick up Pettus's point: filtering out precisely and only the noise is hard. Maybe in a couple more decades we'll be there. (Sorry I won't be around for it.) For now ignoring it might be the best option.
On 1/15/21 11:43 PM, Hemil Ruparel wrote:
Exactly my point. We need to raise the bar of the behavior we tolerate. This should not be tolerated. We need to set an example. The person in question clearly understood english and I have never seen a person who could use mailing lists but not google. So that's out of the question.
We are not free consultants. And you are not entitled to shit. You are probably being paid to work on that project. We are not. Your problem. Fix it yourself. Or at least have to courtesy to google it.
I watched this sadness play out. It had nothing to do with the OP's original question. Rather someone with feelings hurt from a separate thread (table correlation) felt the need drag that squabble over to the focal issue here (tools). I was tempted bring up the COC but I'm not really a believer.
We see these flare ups almost as frequently as the repetition of the "tune pg tool" request. They die out pretty quickly especially when an obvious expert declines to waste any more of the offender's (offended's) time.
On 1/15/21 10:51 PM, Hemil Ruparel wrote:
This is a meta discussion. I couldn't find a meta mailing list so I am posting it here. This discussion sparked from this message.
We should clearly mention on the postgres mailing list page that people are encouraged to do their own research and that we are a community of people who help for free. And so we expect OP to do basic initial research. And the OP is not entitled to receive an answer as we are not bound by any contract. We spend our personal time away from our busy schedule to help others and we have the right to choose who we give our time to.
Another important point is we need a mechanism to prevent polluting our community. We need to raise the bar a little. Or we become like quora. Where the same question is posted thousands of times with the exact same wording. Stack Exchange has taken it to the extreme to the point that it's become toxic for newbies. We need to be somewhere in between. I propose when the first time someone posts such a question, we give them the benefit of doubt and point them to resources which they should consider before posting. Second time, we warn them not to do this again and use the resources they have at their disposal. The third time we should temporarily ban them (say for a week).
It's my personal opinion. But i personally do not want to deal with entitled people who cannot do basic google searches.