[Feature Request]: Support for INDEX with IGNORE_DUP_KEY=ON

[PauloHMattos]

The applications of my company rely heavily on this option and without it, we are effectively unable to move to babelfish.

Is there any plan to support in the near future?

[Deepesh125]

@PauloHMattos We are already aware about this limitation and is under assessment. Just to get more clarity, how is it absolutely important for your use case, have you tried any alternatives, and (if so) why don't workaround works for your use case? Thank you!

[PauloHMattos]

@Deepesh125 right now we are evaluating performing this inserts directly in the PG INSERT ON CONFLICT DO NOTHING, but we are not sure if there's a recommended way to handle this limitation. Do you know how other users of Babelfish handle this?

To us seems a viable option, but our team is not very knowledgeable of PG and Babelfish in general so there are a lot of unknows. This being supported directly by Babelfish would reduce considerably the risk

Thanks for the help!