Re: pg_replication_origin_xact_reset() and its argument variables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_replication_origin_xact_reset() and its argument variables
Date: 2016-06-30 14:14:04
Message-ID: 19890.1467296044@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> The document explains that pg_replication_origin_xact_reset() doesn't have
> any argument variables. But it's been actually defined so as to have two
> argument variables with pg_lsn and timestamptz data types, as follows.

> =# \df pg_replication_origin_xact_reset
> List of functions
> Schema | Name | Result data type |
> Argument data types | Type
> ------------+----------------------------------+------------------+----------------------------------+--------
> pg_catalog | pg_replication_origin_xact_reset | void |
> pg_lsn, timestamp with time zone | normal

> As far as I read the code of the function, those arguments don't seem to
> be necessary. So I'm afraid that the pg_proc entry for the function might
> be incorrect and those two arguments should be removed from the definition.
> Is this analysis right?

Sure looks that way from here. Copy-and-paste from the previous
line in pg_proc.h, perhaps?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-06-30 14:24:13 Re: primary_conninfo missing from pg_stat_wal_receiver
Previous Message Fujii Masao 2016-06-30 13:17:10 Re: primary_conninfo missing from pg_stat_wal_receiver