From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump multi VALUES INSERT |
Date: | 2018-12-31 09:38:18 |
Message-ID: | CAKJS1f8=qKfNBFK5Y5DG_eoGaCD5SxuukQNpZPOOSeVPPPdemQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Just looking at the v5 patch, it seems not to handle 0 column tables correctly.
For example:
# create table t();
# insert into t default values;
# insert into t default values;
$ pg_dump --table t --inserts --insert-multi=100 postgres > dump.sql
# \i dump.sql
[...]
INSERT 0 1
psql:dump.sql:35: ERROR: syntax error at or near ")"
LINE 1: );
^
I'm not aware of a valid way to insert multiple 0 column rows in a
single INSERT statement, so not sure how you're going to handle that
case.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-12-31 09:50:20 | Re: Clean up some elog messages and comments for do_pg_stop_backup and do_pg_start_backup |
Previous Message | David Rowley | 2018-12-31 08:57:04 | Re: Speeding up creating UPDATE/DELETE generic plan for partitioned table into a lot |