Re: BUG #6710: txid_current() provides incorrect txid after server startup - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #6710: txid_current() provides incorrect txid after server startup
Date
Msg-id 4FEDD928.7080200@enterprisedb.com
Whole thread Raw
In response to BUG #6710: txid_current() provides incorrect txid after server startup  (tarvip@gmail.com)
List pgsql-bugs
On 27.06.2012 10:08, tarvip@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      6710
> Logged by:          Tarvi Pillessaar
> Email address:      tarvip@gmail.com
> PostgreSQL version: 9.1.4
> Operating system:   linux
> Description:
>
> This happens when epoch is greater than 0.
> After a checkpoint it starts providing correct txid.
>
> It seems that this regression is caused by following commit:
> 20d98ab6e4110087d1816cd105a40fcc8ce0a307 Correct epoch of txid_current()
> when executed on a Hot Standby server.
>
> When reverting this commit, txid_current() works as expected.

Fixed, thanks for the report!

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Daniel Farina
Date:
Subject: Re: How to run query by command prompt in Postgres
Next
From: r d
Date:
Subject: Feature Request (and/or possible bug) re Default Tablespaces