Search Postgresql Archives
Re: Using a single sequence for all tables
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Using a single sequence for all tables
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Wed, 29 Sep 2021 10:21:00 -0600
Cc
: "Peter J. Holzer" <hjp-pgsql@xxxxxx>, PostgreSQL General <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to
: <
dc6a27272a280b2ae4358681ca8854dc8661c540.camel@cybertec.at
>
References
: <
YVQxL6YWXxhQwcft@hjp.at
> <
dc6a27272a280b2ae4358681ca8854dc8661c540.camel@cybertec.at
>
If your processes somehow allow updates on the wrong table, then fix that.
If you run out of space in whatever value range you choose initially, the pain to upgrade to a type that allows larger values would seem to be very large.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
Re: Using a single sequence for all tables
From:
Peter J. Holzer
References
:
Using a single sequence for all tables
From:
Peter J. Holzer
Re: Using a single sequence for all tables
From:
Laurenz Albe
Prev by Date:
Re: Using a single sequence for all tables
Next by Date:
ERROR: unrecognized node type
Previous by thread:
Re: Using a single sequence for all tables
Next by thread:
Re: Using a single sequence for all tables
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
