From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, PFC <lists(at)peufeu(dot)com>, Tino Wildenhain <tino(at)wildenhain(dot)de>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: COPY (query) TO file |
Date: | 2006-06-03 16:38:01 |
Message-ID: | 4481BAE9.4000903@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Greg Stark <gsstark(at)mit(dot)edu> writes:
>
>
>>PFC <lists(at)peufeu(dot)com> writes:
>>
>>
>>>MySQL already does this for INSERT :
>>>INSERT INTO x (a,b) VALUES (1,2), (3,4), (5,6)...;
>>>
>>>
>
>
>The above syntax is SQL-standard, so we ought to support it sometime,
>performance benefits or no. I agree it might be tricky to avoid eating
>an unreasonable amount of memory for a very long list in Postgres :-(
>
>Supporting VALUES only in INSERT would be relatively trivial BTW,
>but the spec actually thinks it should be allowed as a <table spec>
>in FROM ...
>
>
>
>
Can we just start with the simple case?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Ganesh Chaudhari | 2006-06-03 16:59:58 | Re: Problem building initdb on sparc10 |
Previous Message | Tom Lane | 2006-06-03 16:36:40 | Re: COPY (query) TO file |