Skip site navigation (1) Skip section navigation (2)

Re: BUG #2712: could not fsync segment: Permission

From: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Thomas H(dot)" <me(at)alternize(dot)com>,"Bruce Momjian" <bruce(at)momjian(dot)us>,<pgsql-bugs(at)postgresql(dot)org>,"Magnus Hagander" <mha(at)sollentuna(dot)net>
Subject: Re: BUG #2712: could not fsync segment: Permission
Date: 2006-10-23 18:59:39
Message-ID: 453D2D35.E840.00BE.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
That might be one cause (or it might otherwise exacerbate the problem),
but it isn't the only cause.  We weren't running anti-virus software and
neither is Thomas.  Unfortunately with the last go around, we
collectively ran out of ideas before an underlying cause could be
identified.

Pete

>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 23.10.2006 19:49 >>>
installed), but there is no known reason other than antivirus software
for the "could not fsync" problem.


In response to

pgsql-bugs by date

Next:From: Peter BrantDate: 2006-10-23 19:24:25
Subject: Re: BUG #2712: could not fsync segment: Permission
Previous:From: Thomas H.Date: 2006-10-23 18:00:11
Subject: Re: BUG #2712: could not fsync segment: Permission

pgsql-patches by date

Next:From: Tom LaneDate: 2006-10-23 19:08:03
Subject: Re: [PATCHES] smartvacuum() instead of autovacuum
Previous:From: Jim C. NasbyDate: 2006-10-23 18:36:28
Subject: Re: [PATCHES] smartvacuum() instead of autovacuum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group