| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | glen(dot)edmonds(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17428: last_value incorrect for uninitialized sequence |
| Date: | 2022-03-07 14:48:05 |
| Message-ID: | 189261.1646664485@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Mon, Mar 7, 2022 at 12:15 AM PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>> For a freshly defined sequence, the following:
>> select last_value from mytable_id_seq
>> should return 0, but returns 1.
> One seems as good a choice as zero if a non-null value is to be returned.
The larger point here is that any change is much more likely to
break applications expecting the historical behavior than it is
to make anyone's life better. In a green field I'd tend to
agree that returning NULL (and dispensing with is_called) would
be a better design, but that opportunity was missed decades ago.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glen Edmonds | 2022-03-07 15:14:44 | Re: BUG #17428: last_value incorrect for uninitialized sequence |
| Previous Message | David G. Johnston | 2022-03-07 13:35:24 | Re: BUG #17428: last_value incorrect for uninitialized sequence |