Re: Libpq PGRES_COPY_BOTH - version compatibility - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Libpq PGRES_COPY_BOTH - version compatibility
Date
Msg-id FB92E9D1-C6C5-4444-8FF7-3CA20EF74FB3@gmail.com
Whole thread Raw
In response to Re: Libpq PGRES_COPY_BOTH - version compatibility  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Mar 27, 2011, at 4:09 PM, Magnus Hagander <magnus@hagander.net> wrote:
> That doesn't mean we shouldn't do this (haven't reconsidered the whole
> thread) - but it doesn't solve the issue I originally raised.

I'm somewhat inclined to just remove this from the list of open items. It doesn't seem clear what the action item is
here,or even that there is one, so holding up beta for it doesn't seem right.  When/if we figure out what needs to be
done,we can revisit the issue. 

Anyone disagree?

...Robert

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Libpq PGRES_COPY_BOTH - version compatibility
Next
From: David Fetter
Date:
Subject: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is