On Thu, Jan 20, 2011 at 6:14 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> So I'm not sure whether to fix it, or leave it as a known failure case
> in old branches.  Comments?

Since there is a workaround, I think it is best to document it and
leave it as-is.

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to