Skip site navigation (1) Skip section navigation (2)

Re: BUG #6213: COPY does not work as expected in a plpgsql function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Ramanujam <innomotive(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6213: COPY does not work as expected in a plpgsql function
Date: 2011-09-26 14:33:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Robert Haas <robertmhaas(at)gmail(dot)com> 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 parsing/execution of the sub-SELECT.  It might be relatively
straightforward to fix, or then again it might not.  The parsing end of
it could quite likely be harder than the execution end.  We've
surmounted similar issues in places like EXPLAIN, though.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Daniel Cristian CruzDate: 2011-09-26 14:34:44
Subject: BUG #6225: Child table with a missing parent key which no exists in a complex trigger/cascade schema
Previous:From: Peter EisentrautDate: 2011-09-26 14:30:32
Subject: Re: [v9.2] make_greater_string() does not return a string in some cases

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group