Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem. - Mailing list pgsql-bugs

From Sean Chittenden
Subject Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.
Date
Msg-id 20030508045749.GV49916@perrin.int.nxad.com
Whole thread Raw
In response to Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.  (johnnnnnn <john@phaedrusdeinus.org>)
List pgsql-bugs
> > I suspect that a good number of fairly simple questions aren't
> > being answered because they're either misdirected or because the
> > poster hasn't included an "answerable" question (one with
> > sufficient information to answer).
>
> That's always been a problem, but it does seem to have been getting
> worse lately.

I hate to point this out, but "TIP 4" is getting a bit old and the 6
tips that we throw out to probably about 40K people about 1-200 times
a day have probably reached saturation.  Without looking at the
archives, I bet anyone a shot of good scotch that, it's probably
pretty infrequent that people don't kill -9 their postmasters.

Any chance we could flush out the TIPs at the bottom to include,
"VACUUM ANALYZE your database regularly," or "When reporting a
problem, include the output from EXPLAIN [query]," or "ANALYZE tables
before examining the output from an EXPLAIN [query]," or "Visit [url]
for a tutorial on (schemas|triggers|views)."

-sc

--
Sean Chittenden


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] [SQL] Unanswered Questions WAS: An unresolved performance problem.
Next
From: "A.Bhuvaneswaran"
Date:
Subject: pg_dumpall segmentation fault