| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Steve Singer <steve(at)ssinger(dot)info>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
| Subject: | Re: sequence data type |
| Date: | 2017-03-29 17:36:51 |
| Message-ID: | e0092389-e625-91fe-5c42-fc3443773bad@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Over at
<https://www.postgresql.org/message-id/CAKOSWNnXmM6YBXNzGnXtZQMPjDgJF+a3Wx53Wzmrq5wqDyRX7Q@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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Adjust-min-max-values-when-changing-sequence-type.patch | invalid/octet-stream | 11.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-29 17:40:29 | Re: identity columns |
| Previous Message | Arthur Zakirov | 2017-03-29 17:14:27 | Re: [PATCH] Generic type subscripting |