Re: age(xid) on hot standby

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: age(xid) on hot standby
Date: 2012-01-17 01:59:00
Message-ID: 1326765506-sup-209@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Tom Lane's message of lun ene 16 12:27:03 -0300 2012:
>
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Excerpts from Peter Eisentraut's message of dom ene 15 10:00:03 -0300 2012:
> >> On ons, 2011-12-28 at 14:35 -0500, Tom Lane wrote:
> >>> The trouble with using ReadNewTransactionId is that it makes the results
> >>> volatile, not stable as the function is declared to be.
>
> >> Could we alleviate that problem with some caching within the function?
>
> > Maybe if we have it be invalidated at transaction end, that could work.
> > So each new transaction would get a fresh value.
>
> Yeah, I think that would work.

So who's going to work on a patch? Peter, are you? If not, we should
add it to the TODO list.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2012-01-17 01:59:08 Re: Checkpoint sync pause
Previous Message Robert Haas 2012-01-17 01:27:19 Re: Why is CF 2011-11 still listed as "In Progress"?