BUG #16989: parameter track_commit_timestamp's category problem

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: leiyanliang(at)highgo(dot)com
Subject: BUG #16989: parameter track_commit_timestamp's category problem
Date: 2021-04-30 08:58:12
Message-ID: 16989-22817aa1c984d7dc@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16989
Logged by: yanliang lei
Email address: leiyanliang(at)highgo(dot)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?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bharath Rupireddy 2021-04-30 09:33:55 Re: BUG #16989: parameter track_commit_timestamp's category problem
Previous Message Noah Misch 2021-04-30 03:15:01 Re: BUG #16939: Plural interval for negative singular