Re: DOCS: Missing tags for some SEQUENCE fields - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: DOCS: Missing tags for some SEQUENCE fields
Date
Msg-id CAA4eK1+NnLiFPpgcFMkas-4AOn-G0==XqO5AHHGkmO=CqU5anw@mail.gmail.com
Whole thread Raw
In response to Re: DOCS: Missing tags for some SEQUENCE fields  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: DOCS: Missing tags for some SEQUENCE fields
List pgsql-hackers
On Thu, Nov 13, 2025 at 4:46 PM Chao Li <li.evan.chao@gmail.com> wrote:
> > On Nov 13, 2025, at 13:17, Peter Smith <smithpb2250@gmail.com> wrote:
> >
> > Hi,
> >
> > While reviewing the recent patches for SEQUENCE documentation I found
> > [1] a few more instances where the <structfield> tag should have been
> > used for some of the sequence fields (per the recent push [2]).
> >
>
> Good catch. LGTM. I rendered the html pages and viewed them, the pages also look good.
>

Why do we think using <structfield> tag is appropriate instead of the
current <literal> tag? The explanation of the is_called says: "Sets
the sequence object's current value, and optionally its is_called
flag.", so from "object's current value", are we deducing it is the
same as struct? Ideally, it should be used to mark up the name of a
field in a struct which is close to what we are doing here. Do we have
a similar usage at other places in the docs?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Next
From: 高增琦
Date:
Subject: Compile error on the aarch64 platform: Missing asm/hwcap.h