From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Functions with COPY |
Date: | 2003-11-28 18:02:56 |
Message-ID: | 20031128180256.GJ24094@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > No, I'm interested, as I discussed in my message[1], in the ability to
> > use functions in a copy statement to allow me to specify the conversion
> > from text to the appropriate data type.
>
> COPY is not intended to be that flexible; it's intended to be fast.
I wouldn't expect much of a speed difference between to_date() and
cast(text as date). Is there some reason I'm not seeing to expect it to
be much slower? My guess was that supporting this wouldn't involve
that much code change either but I'm probably wrong.
> You can do any amount of processing you want in an INSERT statement,
> though.
Certainly, but for bulk loads that requires more pre-processing work for
the user and I believe results in more work for the server too (it
certainly takes longer...).
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2003-11-28 18:05:38 | Re: about explain analyze |
Previous Message | Marc G. Fournier | 2003-11-28 17:59:08 | Re: about explain analyze |