RE: ON CONFLICT DO NOTHING on pg_dump - Mailing list pgsql-hackers

From Ideriha, Takeshi
Subject RE: ON CONFLICT DO NOTHING on pg_dump
Date
Msg-id 4E72940DA2BF16479384A86D54D0988A6F14B74E@G01JPEXMBKW04
Whole thread Raw
In response to Re: ON CONFLICT DO NOTHING on pg_dump  (Surafel Temesgen <surafel3000@gmail.com>)
Responses Re: ON CONFLICT DO NOTHING on pg_dump  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Hi,

>    The new structure member appears out of place, can you move up along
>    with other "command-line long options" ?
>
>
>
>Done
>

I did regression tests (make check-world) and 
checked manually pg_dump --on-conflict-do-nothing works properly.
Also it seems to me the code has no problem.
This feature has advantage to some users with small code change.

So I marked it as 'Ready for committer'.
I'd like to wait and see committers opinions.

Regards,
Takeshi Ideriha


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: user-friendliness improvement of pageinspect
Next
From: Amit Kapila
Date:
Subject: Re: Concurrency bug in UPDATE of partition-key