| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Sequence Access Methods, round two |
| Date: | 2024-01-18 15:05:58 |
| Message-ID: | a952d7c0-75ac-46ed-b64f-bba728c2d421@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01.12.23 06:00, Michael Paquier wrote:
> Please find attached a patch set that aims at implementing sequence
> access methods, with callbacks following a model close to table and
> index AMs, with a few cases in mind:
> - Global sequences (including range-allocation, local caching).
> - Local custom computations (a-la-snowflake).
That's a lot of code, but the use cases are summarized in two lines?!?
I would like to see a lot more elaboration what these uses cases are (I
recognize the words, but do we have the same interpretation of them?)
and how they would be addressed by what you are proposing, and better
yet an actual implementation of something useful, rather than just a
dummy test module.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-01-18 15:09:11 | Re: Emit fewer vacuum records by reaping removable tuples during pruning |
| Previous Message | Magnus Hagander | 2024-01-18 15:01:33 | Re: System username in pg_stat_activity |