| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| Date: | 2015-05-29 22:29:46 |
| Message-ID: | CA+TgmoY2ue7BezuZUCt3m5kkVu3nxhVemj6V_H1mAWwS6x5jYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, May 29, 2015 at 5:14 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Just saw what looks like a report of this issue on 9.2.
>
> https://github.com/wal-e/wal-e/issues/177
Urk. That looks awfully similar, but I don't think any of the code
that is affected here exists in 9.2, or that any of the fixes involved
were back-patched to 9.2. So that might be something else altogether.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2015-05-29 22:41:01 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| Previous Message | Steve Kehlet | 2015-05-29 21:32:41 | Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-29 22:33:21 | Re: [CORE] postpone next week's release |
| Previous Message | Bruce Momjian | 2015-05-29 22:28:01 | Re: [CORE] postpone next week's release |