Robert Haas writes:
> It would actually be nice if worked even without that, but I'm not
> sure what would be involved in making that happen.
I've been too busy to look at this in detail, but I imagine the issue is
failure to pass parameters down from the ProcessUtility call to COPY
into the pars
On Mon, Sep 26, 2011 at 12:45 AM, Ramanujam wrote:
> On Mon, Sep 26, 2011 at 9:57 AM, Robert Haas wrote:
>> Does it work if you use EXECUTE?
>
> Apologies to have not included the list when I replied to Pavel.
> Re-writing it as a dynamic sql stmt indeed works. Sorry for the noise.
Ah, OK. No p
On Mon, Sep 26, 2011 at 9:57 AM, Robert Haas wrote:
> Does it work if you use EXECUTE?
Apologies to have not included the list when I replied to Pavel.
Re-writing it as a dynamic sql stmt indeed works. Sorry for the noise.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
On Sun, Sep 18, 2011 at 10:55 PM, Ramanujam wrote:
> The following bug has been logged online:
>
> Bug reference: 6213
> Logged by: Ramanujam
> Email address: innomot...@gmail.com
> PostgreSQL version: 9.0
> Operating system: linux x86_64
> Description: COPY does not wo
The following bug has been logged online:
Bug reference: 6213
Logged by: Ramanujam
Email address: innomot...@gmail.com
PostgreSQL version: 9.0
Operating system: linux x86_64
Description:COPY does not work as expected in a plpgsql function
Details:
A function like th
