agora inbox for pgsql-docs@postgresql.org  

help / color / mirror / Atom feed

From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: pgsql-docs@lists.postgresql.org
Subject: Re: Minor documentation fixes related to v18
Date: Wed, 25 Jun 2025 00:28:56 +0900
Message-ID: <c2826683-ec8b-418a-817b-279c13e3f9cb@oss.nttdata.com> (raw)
In-Reply-To: <e95c899a-2aeb-45b7-8fd3-7a27dcdb475b@oss.nttdata.com>
References: <e95c899a-2aeb-45b7-8fd3-7a27dcdb475b@oss.nttdata.com>



On 2025/06/19 19:34, Fujii Masao wrote:
> Hi,
> 
> I'd like to propose three minor documentation fixes related to parameters
> introduced in v18. Since they align with new content in that version,
> I'm thinking to apply them to v18. Thoughts?
> 
> 0001:
> For parameters that exist as both configuration and storage options,
> the documentation usually includes secondary index entries to help users
> find them easily. However, such entries were missing for vacuum_truncate
> and vacuum_max_eager_freeze_failure_rate. This patch adds the appropriate
> index terms.
> 
> 0002:
> The description of track_cost_delay_timing lists where cost-based vacuum
> delay timing information is shown when the setting is enabled. Although
> this information also appears in ANALYZE VERBOSE output, that wasn't
> mentioned. This patch adds it to the list.
> 
> 0003:
> The io_workers parameter was documented with the type "int", but
> the standard format in our docs is "integer". This patch updates it
> for consistency with other GUC parameter descriptions.

These patches are straightforward fixes. Unless there are any objections,
I'll go ahead and commit them.

Regards,

-- 
Fujii Masao
NTT DATA Japan Corporation

view thread (3+ messages)  latest in thread

Message-ID: <c2826683-ec8b-418a-817b-279c13e3f9cb@oss.nttdata.com>
Permalink:  ../c2826683-ec8b-418a-817b-279c13e3f9cb@oss.nttdata.com/
Also on:    postgresql.org/message-id/c2826683-ec8b-418a-817b-279c13e3f9cb@oss.nttdata.com

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Minor documentation fixes related to v18
  In-Reply-To: <c2826683-ec8b-418a-817b-279c13e3f9cb@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox