| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, "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:58:45 |
| Message-ID: | 20150529225845.GD6535@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 2015-05-30 10:55:30 +1200, Thomas Munro wrote:
> That's the error message, but then further down:
Ooops.
> "I have confirmed that directory "pg_multixact/members" does not
> existing in the restored data directory.
>
> I can see this directory and the file if i restore a few days old
> backup. I have used WAL-E backups a number of time from this server
> but this is the first time I am running into this issue."
That sounds like a WAL-E problem rather than a postgres one then. I
think it's exceedingly unlikely - although I perhaps should be careful
with that given the recent history - that postgres contains a bug that
deletes an entire directory on the standby/while cloning.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-05-30 00:18:50 | Re: Planner cost adjustments |
| Previous Message | Thomas Munro | 2015-05-29 22:55:30 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-05-29 23:20:44 | nested loop semijoin estimates |
| Previous Message | Thomas Munro | 2015-05-29 22:55:30 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |