| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer Best Practices |
| Date: | 2015-08-26 19:05:54 |
| Message-ID: | 55DE0E12.5080606@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 26/08/15 12:17, Melvin Davidson wrote:
[...]
> So for the sake of argument, a natural key is something that in itself
> is unique and the possibility of a duplicate does not exist.
> Before ANYONE continues to insist that a serial id column is good,
> consider the case where the number of tuples will exceed a bigint.
> Don't say it cannot happen, because it can.
>
If you create tuples in your table at the rate of a million records per
second every hour of every day of every year, it will take over 250,000
years to exceed the value of a bigint!
[...]
>
>
> --
> *Melvin Davidson*
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.
I will refrain from marking snarky comments about your sig - tempting
though it might be! :-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Flower | 2015-08-26 19:13:33 | Re: PostgreSQL Developer Best Practices |
| Previous Message | George Weaver | 2015-08-26 19:05:46 | Re: PostgreSQL Developer Best Practices |