Re: [HACKERS] Performance testing of COPY (SELECT) TO - Mailing list pgsql-patches

From Jim C. Nasby
Subject Re: [HACKERS] Performance testing of COPY (SELECT) TO
Date
Msg-id 20060830173632.GF81373@pervasive.com
Whole thread Raw
In response to Re: [HACKERS] Performance testing of COPY (SELECT) TO  (Zoltan Boszormenyi <zboszor@dunaweb.hu>)
List pgsql-patches
On Mon, Aug 28, 2006 at 07:35:11PM +0200, Zoltan Boszormenyi wrote:
> >>COPY (SELECT ...) (col1, col2, ...) TO
> >>and it was actually working. In your v9
> >>you rewrote the syntax parsing so that
> >>feature was lost in translation.
> >>
> >
> >Interesting.  I didn't realize this was possible -- obviously I didn't
> >test it (did you have a test for it in the regression tests?  I may have
> >missed it).  In fact, I deliberately removed the column list from the
> >grammar, because it can certainly be controlled inside the SELECT, so I
> >thought there was no reason the support controlling it in the COPY
> >column list.
> >
>
> Yes, it was even documented. I thought about having
> queries stored statically somewhere (not in views) and
> being able to use only part of the result.

ISTM that there should have been a regression test that tried that
capability out. That would have made it obvious when the functionality
was lost, at least.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Interval aggregate regression failure
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] log_statement output for protocol