From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marti Raudsepp <marti@juffo.org>
Cc: Euler Taveira de Oliveira <euler@timbira.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: [PATCH] Fix documentation about PL/Python exception handling
Date: Mon, 15 Nov 2010 15:25:23 -0500
Message-ID: <6240.1289852723@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTikSed65+BL-iwrjKv2isUS-JSwpWVzbH5dAxgAE@mail.gmail.com>
References: <AANLkTinWJoW2Q1VOtb-EL_XV3iOrKNBedTFfbx_zhED-@mail.gmail.com>
<4CDAA73A.6090409@timbira.com>
<AANLkTikSed65+BL-iwrjKv2isUS-JSwpWVzbH5dAxgAE@mail.gmail.com>
Marti Raudsepp <marti@juffo.org> writes:
> On Wed, Nov 10, 2010 at 16:07, Euler Taveira de Oliveira
> <euler@timbira.com> wrote:
>> Sure. But bear in mind that we don't usually backpatch documentation unless
>> there is incorrect information; improvement belongs to HEAD.
> Yeah, it is quite incorrect (as you can see by comparing test results
> from 1st post with the documentation).
> Attached is a documentation patch that will apply to PostgreSQL 8.1 - 8.4
Hmmm ... I'm less than excited about documenting agreed-to-be-broken
behavior in exquisite detail. Doing so will just encourage people to
rely on it. It's particularly unfriendly to document it in detail
without pointing out that it's likely to change.
My inclination is to forget about these doc changes and spend our time
on fixing the behavior instead.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, marti@juffo.org, euler@timbira.com
Subject: Re: [PATCH] Fix documentation about PL/Python exception handling
In-Reply-To: <6240.1289852723@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox