On 31/08/16 16:10, Tom Lane wrote:
> I wrote:
>> Personally, my big beef with the current approach to sequences is that
>> we eat a whole relation (including a whole relfilenode) per sequence.
>> I wish that we could reduce a sequence to just a single row in a
>> catalog, including the nontransactional state. Not sure how feasible
>> that is either, but accomplishing it would move the benefits of making
>> a change out of the "debatable whether it's worth it" category, IMO.
>
> BTW, another thing to keep in mind here is the ideas that have been
> kicked around in the past about alternative sequence implementations
> managed through a "sequence AM API". I dunno whether now is the time
> to start creating that API abstraction, but let's at least consider
> it if we're whacking the catalog representation around.
>
FWIW if I was going to continue with the sequence AM API, the next patch
would have included split of sequence metadata and sequence state into
separate catalogs, so from that point this actually seems like an
improvement (I didn't look at the code though).
As a side note, I don't plan to resurrect the seqam patch at least until
we have reasonable built-in logical replication functionality.
-- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services