RE: ON CONFLICT DO NOTHING on pg_dump

From: "Ideriha, Takeshi" <ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com>
To: Surafel Temesgen <surafel3000(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Subject: RE: ON CONFLICT DO NOTHING on pg_dump
Date: 2018-07-11 02:20:40
Message-ID: 4E72940DA2BF16479384A86D54D0988A6F14B74E@G01JPEXMBKW04
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2018-07-11 03:26:23 Re: Concurrency bug in UPDATE of partition-key
Previous Message Peter Geoghegan 2018-07-11 02:08:46 Re: user-friendliness improvement of pageinspect