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)...;

> Does MySQL really let you stream that? Trying to do syntax like that in
> Postgres wouldn't work because the parser would try to build up a parse tree
> for the whole statement before running the command.

A quick look at MySQL's grammar doesn't show any indication that they
don't build a full parse tree too.

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 ...

			regards, tom lane

In response to

• Re: COPY (query) TO file at 2006-06-03 14:22:19 from Greg Stark

Responses

• Re: COPY (query) TO file at 2006-06-03 15:45:52 from Greg Stark
• Re: COPY (query) TO file at 2006-06-03 16:38:01 from Andrew Dunstan

pgsql-hackers by date

Next:	From: PFC	Date: 2006-06-03 14:59:29
	Subject: Re: COPY (query) TO file
Previous:	From: Jim Nasby	Date: 2006-06-03 14:42:03
	Subject: Re: 'CVS-Unknown' buildfarm failures?