| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Surafel Temesgen <surafel3000(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump multi VALUES INSERT |
| Date: | 2019-01-29 09:24:33 |
| Message-ID: | 201901290924.xw464ogexx74@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jan-23, David Rowley wrote:
> On Wed, 23 Jan 2019 at 04:08, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > Is it possible to avoid the special case for 0 columns by using the
> > UNION ALL syntax I showed?
>
> It would be possible, but my thoughts are that we're moving away from
> the SQL standard by doing so.
Ah, that's a good point that I missed -- I agree with your reasoning.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-01-29 09:32:27 | Re: speeding up planning with partitions |
| Previous Message | Alvaro Herrera | 2019-01-29 09:22:36 | Re: move hash_any to utils/hash/hashfn.c |