Re: [HACKERS] Hot Standby utility and administrator functions - Mailing list pgsql-general

From Zeugswetter Andreas OSB sIT
Subject Re: [HACKERS] Hot Standby utility and administrator functions
Date
Msg-id 6DAFE8F5425AB84DB3FCA4537D829A561CE07FCB6C@M0164.s-mxs.net
Whole thread Raw
In response to Re: [HACKERS] Hot Standby utility and administrator functions  ("Robert Haas" <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Hot Standby utility and administrator functions  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-general
> > * pg_last_recovered_xact_xid()
> > Will throw an ERROR if *not* executed in recovery mode.
> > returns bigint
> >
> > * pg_last_completed_xact_xid()
> > Will throw an ERROR *if* executed in recovery mode.
> > returns bigint
>
> Should these return xid?

And shouldn't these two be folded together ?
It seems most usages of this xid(/lsn?) will be agnostic to the
recovery mode. Or if not, it seems more convenient to have a function
that returns both recovery mode and xid, no ?

Andreas

pgsql-general by date:

Previous
From: tomas@tuxteam.de
Date:
Subject: Re: [HACKERS] Debian no longer dumps cores?
Next
From: Ivan Sergio Borgonovo
Date:
Subject: tsearch2: setting weights on tsquery