Re: pg_stat_replication log positions vs base backups

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_replication log positions vs base backups
Date: 2015-11-26 13:53:13
Message-ID: CABUevEy7roL3RD=OVP1fX+4vnKWRWh8=ibz4kodumn=ndhTqdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 26, 2015 at 1:03 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:

> On Thu, Nov 26, 2015 at 6:45 PM, Magnus Hagander wrote:
> > I'm only talking about the actual value in pg_stat_replication here, not
> > what we are using internally. These are two different things of course -
> > let's keep them separate for now. In pg_stat_replication, we explicitly
> > check for InvalidXLogRecPtr and then explicitly set the resulting value
> to
> > NULL in the SQL return.
>
> No objections from here. I guess you already have a patch?
>

Well, no, because I haven't figured out which way is the logical one - make
them all return NULL or make them all return 0/0...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2015-11-26 14:19:07 Re: WIP: About CMake v2
Previous Message Etsuro Fujita 2015-11-26 12:59:52 Re: Foreign join pushdown vs EvalPlanQual