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

Re: [HACKERS] Performance testing of COPY (SELECT) TO

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Böszörményi Zoltán <zboszor(at)dunaweb(dot)hu>,Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO
Date: 2006-08-28 15:03:14
Message-ID: 44F305B2.9080404@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Alvaro Herrera wrote:
> Böszörményi Zoltán wrote:
>   
>> Hi,
>>
>> what's the problem with COPY view TO, other than you don't like it? :-)
>>     
>
> The problem is that it required a ugly piece of code.  Not supporting it
> means we can keep the code nice.  The previous discussion led to this
> conclusion anyway so I don't know why we are debating it again.
>
>   

What is so ugly about it? I haven't looked at the code, but I am curious 
to know.

I also don't recall the consensus being quite so clear cut. I guess 
there is a case for saying that if it's not allowed then you know that 
"COPY relname TO" is going to be fast. But, code aesthetics aside, the 
reasons for disallowing it seem a bit thin, to me.

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-08-28 15:05:17
Subject: Re: Rtree circle ops
Previous:From: Alvaro HerreraDate: 2006-08-28 14:44:36
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO

pgsql-patches by date

Next:From: Andrew DunstanDate: 2006-08-28 15:07:40
Subject: Re: [PATCHES] Another VPATH patch for ecpg
Previous:From: Alvaro HerreraDate: 2006-08-28 14:44:36
Subject: Re: [HACKERS] Performance testing of COPY (SELECT) TO

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