Re: More on elog and error codes

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Christopher Sawtell <csawtell(at)xtra(dot)co(dot)nz>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: More on elog and error codes
Date: 2001-03-20 22:46:55
Message-ID: 3.0.5.32.20010321094655.02852720@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 09:41 21/03/01 +1200, Christopher Sawtell wrote:
>Just that it might be a good idea to incorporate the version / release
>details in some way so that when somebody on the list is squeaking about
>an error message it is obvious to the helper that the advice needed is to
>upgrade from the Cretatious Period version to a modern release, and have
>another go.

This is better handled by the bug *reporting* system; the users can easily
get the current version number from PG and send it with their reports. We
don't really want all the error codes changing between releases.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-20 23:01:21 Re: Beta 6 Regression results on Redat 7.0.
Previous Message Philip Warner 2001-03-20 22:43:52 Re: More on elog and error codes