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

From Surafel Temesgen
Subject Re: pg_dump multi VALUES INSERT
Date
Msg-id CALAY4q-BUdc9cBLAwL9UeqgOGZJmcH9ERm+OekpvkQBng1=1ew@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump multi VALUES INSERT  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: pg_dump multi VALUES INSERT
List pgsql-hackers


On Fri, Dec 28, 2018 at 6:46 PM Fabien COELHO <coelho@cri.ensmp.fr> wrote:

> At first i also try to do it like that but it seems the function will
> became long and more complex to me

Probably. But calling it with size 100 should result in the same behavior,
so it is really just an extension of the preceeding one? Or am I missing
something?


Specifying table data using single value insert statement and user specified values insert statement
have enough deference that demand to be separate function and they are not the same thing that should implement
with the same function. Regarding code duplication i think the solution is making those code separate function
and call at appropriate place.

Regards
Surafel

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)
Next
From: Pavel Stehule
Date:
Subject: Re: PostgreSQL vs SQL/XML Standards