On 02/11/13 22:26, Tom Lane wrote:
> It was not, and won't be; the changes required to fix it properly
> seemed too invasive to back-patch, especially considering that you can
> easily avoid the bug.
That's the kind of sensible pragmatism that keeps me feeling happy about
Postgres :-)
Cheers,
Peter
