| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | tarvip(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6710: txid_current() provides incorrect txid after server startup |
| Date: | 2012-06-29 16:34:48 |
| Message-ID: | 4FEDD928.7080200@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 27.06.2012 10:08, tarvip(at)gmail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6710
> Logged by: Tarvi Pillessaar
> Email address: tarvip(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | r d | 2012-06-29 19:49:57 | Feature Request (and/or possible bug) re Default Tablespaces |
| Previous Message | Daniel Farina | 2012-06-28 18:57:23 | Re: How to run query by command prompt in Postgres |