| From: | "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> |
|---|---|
| To: | "Thomas H(dot)" <me(at)alternize(dot)com>,<pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #2712: could not fsync segment: Permission |
| Date: | 2006-10-23 19:24:25 |
| Message-ID: | 453D3309.E840.00BE.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Move to Linux. :-) In our case, everything but the database servers
were already Linux so it was an easy choice. Things have been rock
solid since then.
Once things get stuck, I don't think there is an alternative besides
"stop -m immediate". However, since the problem is caused by an idle
backend holding onto an old WAL segment, maybe having your middle
tier/connection pool close and reopen the connections to the database
every so often would function as a workaround. Somebody with more
knowledge of PG internals than I would have to define "every so often"
though (if the idea is viable at all).
Pete
>>> "Thomas H." <me(at)alternize(dot)com> 23.10.2006 20:00 >>>
is there any workaround? how did you get around that problem of having
a
total lockdown?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-23 19:47:14 | Re: BUG #2712: could not fsync segment: Permission |
| Previous Message | Peter Brant | 2006-10-23 18:59:39 | Re: BUG #2712: could not fsync segment: Permission |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2006-10-23 19:43:47 | COPY does not work with regproc and aclitem |
| Previous Message | Tom Lane | 2006-10-23 19:08:03 | Re: [PATCHES] smartvacuum() instead of autovacuum |