Message-ID: <4CE5EF2E.6040108@2ndquadrant.com>
Date: Thu, 18 Nov 2010 22:29:50 -0500
From: Greg Smith <greg@2ndquadrant.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Marti Raudsepp <marti@juffo.org>,
	Euler Taveira de Oliveira <euler@timbira.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: [PATCH] Fix documentation about PL/Python exception handling
References: <AANLkTinWJoW2Q1VOtb-EL_XV3iOrKNBedTFfbx_zhED-@mail.gmail.com>
	<4CDAA73A.6090409@timbira.com>
	<AANLkTikSed65+BL-iwrjKv2isUS-JSwpWVzbH5dAxgAE@mail.gmail.com>
	<6240.1289852723@sss.pgh.pa.us>
In-Reply-To: <6240.1289852723@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> 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.
>   

The open question for this one then is the right way for exceptions to 
act.  Marti, since you've looked at this a bit already, any thoughts on 
what that should look like?  You initially commented that what happens 
was surprising, but I'm not clear on what you expected to happen instead.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services and Support        www.2ndQuadrant.us