| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pabloa98 <pabloa98(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Could postgres12 support millions of sequences? (like 10 million) |
| Date: | 2020-03-21 03:29:09 |
| Message-ID: | CAKFQuwbo029fGfcsPkVhoA5Kd_c9n_2jmAbsjXHwpySKuQ3nZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday, March 20, 2020, pabloa98 <pabloa98(at)gmail(dot)com> wrote:
>
> If there is another solution different than millions of sequences that do
>> not block, generate few gaps (and those gaps are small) and never generate
>> collisions then I will happily use it.
>
>
You are going to have to lose the not blocking requirement, or at least
define what blocking and non-blocking interactions look like.
What does it mean that bid# 123 exists? Can you, by way of example, just
create a table of all possible bid numbers and update a null column with a
timestamp saying “this bid came into existence at this moment”?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John W Higgins | 2020-03-21 04:04:12 | Re: Could postgres12 support millions of sequences? (like 10 million) |
| Previous Message | pabloa98 | 2020-03-21 03:13:03 | Re: Could postgres12 support millions of sequences? (like 10 million) |