Re: pg_dump multi VALUES INSERT - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pg_dump multi VALUES INSERT
Date
Msg-id alpine.DEB.2.21.1903020730480.8095@lancre
Whole thread Raw
In response to Re: pg_dump multi VALUES INSERT  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: pg_dump multi VALUES INSERT
Re: pg_dump multi VALUES INSERT
Re: pg_dump multi VALUES INSERT
List pgsql-hackers
Hello David & Surafel,

> I think this can be marked as ready for committer now, but I'll defer
> to Fabien to see if he's any other comments.

Patch v16 applies and compiles cleanly, local and global "make check" 
are ok. Doc build is ok.

I did some manual testing with limit cases which did work. Good.

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.

Option "--help" line: number of row*s* ?

About the output: I'd suggest to indent one line per row, something like:

   INSERT INTO foo VALUES
     (..., ..., ..., ...),
     (..., ..., ..., ...),
     (..., ..., ..., ...);

so as to avoid very very very very very very very very very very very very 
very very very very long lines in the output.

I'd suggest to add test tables with (1) no rows and (2) no columns but a 
few rows, with multiple --table options.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: jsonpath
Next
From: Alexander Korotkov
Date:
Subject: Re: WIP: BRIN multi-range indexes