Re: DOCS: What SGML markup to use for user objects like tables, columns, etc?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DOCS: What SGML markup to use for user objects like tables, columns, etc?
Date: 2025-11-09 22:59:19
Message-ID: aREcx3nVx_jgC-MV@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 10, 2025 at 08:30:47AM +1100, Peter Smith wrote:
> On Sun, Nov 9, 2025 at 1:50 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > On Tue, Nov 4, 2025 at 02:35:29PM +1100, Peter Smith wrote:
> > > On Thu, Jul 24, 2025 at 2:18 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > ...
> > > > You are right that we are inconsistent. I think <structname> is the
> > > > accepted way to reference table names, and <structfield> for column
> > > > names. If you can create a patch to make them consistent, I can apply
> > > > it.
> > >
> > > Thanks for offering to apply the patch. It has been available for a
> > > few months now.
> >
> > My apologies for not getting to this sooner. (Seems I need to review
> > all my saved emails for these type of items.) Patch applied to master.
> > Nice improvement.
> >
>
> Thanks for pushing!
>
> I updated the CF entry -- https://commitfest.postgresql.org/patch/6063/#

Thanks!

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Haruna Miwa 2025-11-10 00:40:43 Add MERGE and VALUES statements to tab completion for PREPARE
Previous Message Mihail Nikalayeu 2025-11-09 22:51:51 Re: isolation tester limitation in case of multiple injection points in a single command