From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY FROM view |
Date: | 2006-08-22 00:26:10 |
Message-ID: | 200608220026.k7M0QB707321@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
So we don't want COPY FROM VIEW in 8.2? Even if we later support COPY
(SELECT ...), aren't we still going to want to copy from a view? I
guess not because you would just do COPY (SELECT * FROM view)?
---------------------------------------------------------------------------
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > I've been having the COPY FROM patch that was posted on pgsql-patches
> > some time ago (I think from Hannu Krossing), sitting on my machine, with
> > the intention to commit it for 8.2. However there's something I'm not
> > very sure about -- the patch creates an execution plan by passing a
> > literal "SELECT * FROM view" to pg_parse_query, pg_analyze_and_rewrite,
> > and finally planner().
>
> > I'm sure we can make this work appropiately, patching over the quoting
> > issues that the patch doesn't deal with, but I'm unsure if this is an
> > acceptable approach. (Actually I think it isn't.) But what is an
> > acceptable way to do it?
>
> It seems to me that we had decided that "COPY FROM VIEW" is not even the
> conceptually right way to think about the missing feature. It forces
> you to create a view (at least a temporary one) in order to do what you
> want. Furthermore it brings up the question of why can't you COPY TO
> VIEW. The correct way to think about it is to have a way of dumping the
> output of any arbitrary SELECT statement in COPY-like format.
>
> There was some previous discussion of exactly how to go about that;
> check the archives. Offhand I think we might have liked the syntax
> COPY (parenthesized-SELECT-statement) TO ...
> but there was also some argument in favor of using a separate statement
> that basically "sets the output mode" for a subsequent SELECT. I'm
> not sure if anyone thought about how it would play with psql's \copy
> support, but that's obviously something to consider.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-22 00:28:27 | Re: Use of backslash in tsearch2 |
Previous Message | Jeremy Kronuz | 2006-08-22 00:19:48 | Re: ISBN/ISSN/ISMN/EAN13 module |