Re: Sequence Access Methods, round two - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Sequence Access Methods, round two
Date
Msg-id CALdSSPj5TUM6vi=DtzUVRw9XvRwsToy4QyE2uFY=NeDiNNXmiw@mail.gmail.com
Whole thread Raw
In response to Re: Sequence Access Methods, round two  (Kirill Reshke <reshkekirill@gmail.com>)
Responses Re: Sequence Access Methods, round two
List pgsql-hackers
On Mon, 18 Aug 2025 at 18:15, I wrote:

> I have a small enhancement to the patch set.


I played with patch sets some more, trying to break things in nasty
ways (something like CREATE OPERATOR FAMILY ff USING seqlocal or other
incorrect ddl).
But I had no success. I will try some more later, maybe I will find something

But while doing so I noticed another small enhancement for the patch
set. This change is not that big, so attaching as diff.

PFA diff which describes the access method of sequence on \d+ psql
meta-command likewise we do it for tables.

Example:
```
reshke=# \d+ dd
                             Sequence "public.dd"
  Type  | Start | Minimum |       Maximum       | Increment | Cycles? | Cache
--------+-------+---------+---------------------+-----------+---------+-------
 bigint |     1 |       1 | 9223372036854775807 |         1 | no      |     1
Access method: seqlocal

reshke=# \d+ s4
                             Sequence "public.s4"
  Type  | Start | Minimum |       Maximum       | Increment | Cycles? | Cache
--------+-------+---------+---------------------+-----------+---------+-------
 bigint |     1 |       1 | 9223372036854775807 |         1 | no      |     1
Access method: aa
```


-- 
Best regards,
Kirill Reshke

Attachment

pgsql-hackers by date:

Previous
From: Daniil Davydov
Date:
Subject: Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue
Next
From: Julien Rouhaud
Date:
Subject: Re: Plan caching and serialization for reuse across executions