Re: Fix sequence membership command in PG19 release notes

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, rh(at)vonng(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Fix sequence membership command in PG19 release notes
Date: 2026-10-27 22:33:24
Message-ID: auEmtB4BuXKX_Niy@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, Oct 28, 2026 at 09:30:12AM +1100, Peter Smith wrote:
> > I realize "enabled" could be an overused concept in this text, but using
> > something like:
> >
> > This occurs during the ALL SEQUENCES clause.
> > This happens when the ALL SEQUENCES clause.
> > This is achieved by the ALL SEQUENCES clause.
> >
> > seem much less clear than the existing text.
>
> Oh, I didn't mean for those suggestions to be taken literally. The
> ellipsis "..." and "etc." were supposed to mean -- choose any
> replacement wording you want that avoids saying "enabled".
>
> e.g.
> This is done using the ALL SEQUENCES clause.
> This is done using the REFRESH SEQUENCES clause.

Uh, "This is done" seems very imprecise. Even "This is accomplished"
seems worse.

--
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-docs by date

  From Date Subject
Next Message Arvind Kandpal 2026-10-28 08:15:00 Re: 4.1.4. Special Characters
Previous Message Peter Smith 2026-10-27 22:30:12 Re: Fix sequence membership command in PG19 release notes