On Thu, Mar 30, 2017 at 2:36 AM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > Over at > <https://www.postgresql.org/message-id/cakoswnnxmm6ybxnzgnxtzqmpjdgjf+a3wx53wzmrq5wqdyr...@mail.gmail.com> > is is being discussed that maybe the behavior when altering the sequence > type isn't so great, because it currently doesn't update the min/max > values of the sequence at all. So here is a patch to update the min/max > values when the old min/max values were the min/max values of the data type.
Looks sane to me. The only comment I have would be to add a test to trigger as well the code path of reset_min_value with MINVALUE. -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers