Re: Best tools to monitor and fine tune postgres

And basically you are improving your knowledge as you are expecting those
questions the answers of which you dont know about.

Thats why you seem to not to be helpful and somehow stopping others to not
to be helpful.

I don’t find find it wrong if any new guy asking the question that has been
repeated 1000 times earlier, if I know the answer I WILL RESPOND 1000
TIMES, “unlike you”.

On Friday, January 15, 2021, Atul Kumar <akumar14871(at)gmail(dot)com> wrote:

> Again Thanks alot David for ur response.
>
> You expect everyone to be perfect which cannot happen.
>
> And related to thread, if someone has joined this thread today then it is
> obvious that he may not be able to find the previous threads as well.
>
>
>
>
> Regards
> Atul
>
> On Friday, January 15, 2021, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
>
>> On Fri, Jan 15, 2021 at 8:56 AM Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
>>
>>> Hi o1bigtenor,
>>>
>>> Now what will you say about below query that he should have come with
>>> some research before asking here ?
>>>
>>
>> Yes. The question gets asked frequently so if one searches the archive
>> usually you'll get a thread from the past 6 months or so which is usually
>> recent enough. Plus lots of people publish blog posts and articles on the
>> topic, which are probably more well written and researched than
>> off-the-cuff replies to a mailing list would be. At least posting "hey, I
>> found these three tools, and am leaning toward such-and-such because of
>> reasons, does anyone have any thoughts I should consider?" would should the
>> effort and allow for better responses since at least some background is
>> given. Knowing generally how the poster uses PostgreSQL also helps and
>> should be included.
>>
>> A posting like this I'll usually just ignore since I know that answers
>> already exist to be found, and it is not something that I have chosen to
>> become a "librarian/interactive assistant" for - I relegate to the
>> documentation for that.
>>
>> David J.
>>
>>