pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16989: parameter track_commit_timestamp's category problem
2+ messages / 2 participants
[nested] [flat]
* BUG #16989: parameter track_commit_timestamp's category problem
@ 2021-04-30 08:58 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2021-04-30 08:58 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: leiyanliang@highgo.com
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？
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #16989: parameter track_commit_timestamp's category problem
@ 2021-04-30 09:33 Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Bharath Rupireddy @ 2021-04-30 09:33 UTC (permalink / raw)
To: leiyanliang@highgo.com; pgsql-bugs@lists.postgresql.org
On Fri, Apr 30, 2021 at 2:38 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> 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？
Thanks for reporting. It looks like it is correctly categorized in the
docs under "Replication / Sending Servers", whereas as in the code
guc.c, it is still put under "Replication". You may want to check the
thread at [1] where it's being actively discussed and Justin Pryzby
has a patch for fixing this.
[1] - https://www.postgresql.org/message-id/20210413123139.GE6091%40telsasoft.com
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-04-30 09:33 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-04-30 08:58 BUG #16989: parameter track_commit_timestamp's category problem PG Bug reporting form <noreply@postgresql.org>
2021-04-30 09:33 ` Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
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