| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lanyon" <tom(at)netspot(dot)com(dot)au> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: fsync error when restoring from archived xlogs |
| Date: | 2007-06-19 21:18:30 |
| Message-ID: | 1182287910.6855.360.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2007-06-18 at 16:06 +0930, Tom Lanyon wrote:
> Trying to do a PITR on postgres 8.1.8; I've restored the last full
> backup of the cluster dir and put the required WAL files into place.
This problem is fixed in 8.1.9. Seems it was inadvertently introduced in
8.1.7 (Jan 2007) and was not reported as a bug until after 8.1.8 was
out, in early April.
The 8.1.9 release notes make no mention of the bug fix, which isn't very
helpful, I'll agree.
> Jun 18 15:44:39 postgres[29730]: [54-1] LOG: could not fsync segment
> 0 of relation 1663/42607/44092: No such file or directory
> Jun 18 15:44:39 postgres[29730]: [55-1] PANIC: storage sync failed
> on magnetic disk: No such file or directory
It's a duplicate bug. Please check next time before you report.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-06-19 21:27:04 | Re: Re: [GENERAL] Looking for Graphical people for PostgreSQL tradeshow signage |
| Previous Message | Josh Berkus | 2007-06-19 21:10:26 | Re: Re: [GENERAL] Looking for Graphical people for PostgreSQL tradeshow signage |