Re: pg_dump multi VALUES INSERT
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: David Rowley <david.rowley@2ndquadrant.com>, Surafel Temesgen <surafel3000@gmail.com>, Dmitry Dolgov <9erthalion6@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-03-04T15:46:25Z
Lists: pgsql-hackers
On 2019-Mar-02, Fabien COELHO wrote:
> Although I'm all in favor of checking the int associated to the option, I do
> not think that it warrants three checks and messages. I would suggest to
> factor them all as just one check and one (terse) message.
I suggest ("rows-per-insert must be in range 1..%d", INT_MAX), like
extra_float_digits and compression level.
> About the output: I'd suggest to indent one line per row, something like:
>
> INSERT INTO foo VALUES
> (..., ..., ..., ...),
> (..., ..., ..., ...),
> (..., ..., ..., ...);
+1.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Add pg_dumpall --rows-per-insert
- a193cbec1199 12.0 landed
-
pg_dump: allow multiple rows per insert
- 7e413a0f82c8 12.0 landed