Do we need "Diagnostics" sections of SQL command reference pages? - Mailing list pgsql-docs

From Tom Lane
Subject Do we need "Diagnostics" sections of SQL command reference pages?
Date
Msg-id 13339.1061847470@sss.pgh.pa.us
Whole thread Raw
Responses Re: Do we need "Diagnostics" sections of SQL command reference pages?  (Bruno Wolff III <bruno@wolff.to>)
Re: Do we need "Diagnostics" sections of SQL command reference pages?  ("Dan Langille" <dan@langille.org>)
Re: Do we need "Diagnostics" sections of SQL command reference pages?  (Josh Berkus <josh@agliodbs.com>)
Re: Do we need "Diagnostics" sections of SQL command reference  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-docs
I'm starting to look at updating the docs to match 7.4 error message
spellings.  I find that a large part of the work I'll have to do is in
updating the "Diagnostics" (formerly "Outputs") section of the command
reference pages.  I am wondering if it wouldn't be better to just rip
out these sections entirely.  They seem like nearly content-free fluff
to me --- the listings of possible error messages are always incomplete,
often out of date, and arguably useless.  If there is an error message
that's not clear enough by itself, we'd better fix the error message
instead of putting a gloss on it in the reference page.

Comments?

            regards, tom lane

pgsql-docs by date:

Previous
From: Sumaira Maqsood Ali
Date:
Subject: LOCK.tag(figuring out granularity of lock)
Next
From: Bruno Wolff III
Date:
Subject: Re: Do we need "Diagnostics" sections of SQL command reference pages?