On 06/04/16 06:13, Dmitry Dolgov wrote:
On 6 April 2016 at 03:29, Andrew Dunstan <and...@dunslane.net <mailto:and...@dunslane.net>> wrote: Yeah, keeping it but rejecting update of an existing key is my preference too. cheers andrew Yes, it sounds quite reasonable. Here is a new version of patch (it will throw an error for an existing key). Is it better now?
This seems like reasonable compromise to me. I wonder if the errcode should be ERRCODE_INVALID_PARAMETER_VALUE but don't feel too strongly about that.
-- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
