| 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: | 5875.1317047583@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Cristian Cruz | 2011-09-26 14:34:44 | BUG #6225: Child table with a missing parent key which no exists in a complex trigger/cascade schema |
| Previous Message | Peter Eisentraut | 2011-09-26 14:30:32 | Re: [v9.2] make_greater_string() does not return a string in some cases |