| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: age(xid) on hot standby |
| Date: | 2012-01-15 13:00:03 |
| Message-ID: | 1326632403.32048.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2011-12-28 at 14:35 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Excerpts from Peter Eisentraut's message of mié dic 28 15:04:09 -0300 2011:
> >> On a hot standby, this fails with:
> >> ERROR: cannot assign TransactionIds during recovery
>
> > I think we could just have the xid_age call
> > GetCurrentTransactionIdIfAny, and if that returns InvalidXid, use
> > ReadNewTransactionId instead. That xid_age assigns a transaction seems
> > more of an accident than really intended.
>
> 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-01-15 13:14:52 | Re: lots of unused variable warnings in assert-free builds |
| Previous Message | Peter Eisentraut | 2012-01-15 12:53:32 | Re: exit() calls in libraries |