|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Marti Raudsepp <marti(at)juffo(dot)org>|
|Cc:||Euler Taveira de Oliveira <euler(at)timbira(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>|
|Subject:||Re: [PATCH] Fix documentation about PL/Python exception handling|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Marti Raudsepp <marti(at)juffo(dot)org> writes:
> On Wed, Nov 10, 2010 at 16:07, Euler Taveira de Oliveira
> <euler(at)timbira(dot)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
|Next Message||Marti Raudsepp||2010-11-15 21:21:13||Re: [PATCH] Fix documentation about PL/Python exception handling|
|Previous Message||Tom Lane||2010-11-14 19:46:29||Re: Large SGML Cleanup|