| From: | "Thomas H(dot)" <me(at)alternize(dot)com> |
|---|---|
| To: | "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>, <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #2712: could not fsync segment: Permission |
| Date: | 2006-10-23 18:00:11 |
| Message-ID: | 00fe01c6f6cd$163c58a0$0201a8c0@iwing |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
> The same problem exists in 8.1 too. See this thread
its only appearing in 8.2 here, i've just rechecked our logs...
is there any workaround? how did you get around that problem of having a
total lockdown?
thanks,
thomas
>>>> "Thomas H." <me(at)alternize(dot)com> 23.10.2006 18:21 >>>
> there is defenitely something terribly wrong in the windows 8.2b1
> regarding
> file access/locking. 2nd total db lockup today due to file access locks
> (all
> hold by postmaster):
>
> 2006-10-23 17:48:10 LOCATION: exec_simple_query, postgres.c:1007
> 2006-10-23 17:48:14 LOG: 00000: could not rename file
> "pg_xlog/00000001000000040000002E" to
> "pg_xlog/000000010000000400000037", continuing to try
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Brant | 2006-10-23 18:59:39 | Re: BUG #2712: could not fsync segment: Permission |
| Previous Message | Tom Lane | 2006-10-23 17:49:14 | Re: BUG #2712: could not fsync segment: Permission |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-10-23 18:36:28 | Re: [PATCHES] smartvacuum() instead of autovacuum |
| Previous Message | Tom Lane | 2006-10-23 17:49:14 | Re: BUG #2712: could not fsync segment: Permission |