pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: leiyanliang@highgo.com
Subject: BUG #16989: parameter track_commit_timestamp's category problem
Date: Fri, 30 Apr 2021 08:58:12 +0000
Message-ID: <16989-22817aa1c984d7dc@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16989
Logged by:          yanliang lei
Email address:      leiyanliang@highgo.com
PostgreSQL version: 13.1
Operating system:   CentOS7.6
Description:        

In the following sql statement, parameter track_commit_timestamp's category
is Replication,and this “Replication” is a first-level category,and this
“Replication”has  four second-level categories。

postgres=# select category from pg_settings where
name='track_commit_timestamp';
-[ RECORD 1 ]---------
category | Replication

postgres=# 

In the document( postgresql.org/docs/13/runtime-config-replication.html),
parameter track_commit_timestamp is in the “Sending Servers” category
,and,this “Sending Servers” is a second-level category。


so, what is the  track_commit_timestamp’s category?



view thread (2+ messages)  latest in thread

Message-ID: <16989-22817aa1c984d7dc@postgresql.org>
Permalink:  ../16989-22817aa1c984d7dc@postgresql.org/
Also on:    postgresql.org/message-id/16989-22817aa1c984d7dc@postgresql.org

 · 

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-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, leiyanliang@highgo.com
  Subject: Re: BUG #16989: parameter track_commit_timestamp's category problem
  In-Reply-To: <16989-22817aa1c984d7dc@postgresql.org>

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

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