| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, Kirk Wolak <wolakk(at)gmail(dot)com> |
| Cc: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Using CTID system column as a "temporary" primary key |
| Date: | 2023-03-29 19:23:32 |
| Message-ID: | 478a7768-6b11-dda5-ce82-5b9d39aa4923@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/29/23 12:11, Sebastien Flaesch wrote:
> Oh the use of default keyword is new to me, thanks for that.
>
> But to make PostgreSQL more Informix-compatible, zero should have been
> considered as well.
>
1) Why? Down the road to compatibility with some undetermined group of
databases lies mayhem.
2) 0 can be a valid sequence value:
test(5432)=# create sequence zero_test start 0 minvalue 0;
CREATE SEQUENCE
test(5432)=# select * from zero_test ;
last_value | log_cnt | is_called
------------+---------+-----------
0 | 0 | f
Then what do you do?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2023-03-29 20:06:59 | Re: Do BRIN indexes support MIN/MAX? |
| Previous Message | Christophe Pettus | 2023-03-29 19:18:30 | Re: Using CTID system column as a "temporary" primary key |