Re: BUG #2712: could not fsync segment: Permission - Mailing list pgsql-bugs

It seems to me that it's not been included in b3. Tom?

//Magnus=20

> -----Original Message-----
> From: Thomas H. [mailto:me@alternize.com]=20
> Sent: den 8 november 2006 12:59
> To: Magnus Hagander
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #2712: could not fsync segment: Permission
>=20
> magnus, has this fix made it into the 8.2b3 codebase? at=20
> least it fixed 1 of my 3 problems ;-)
>=20
> regards,
> thomas
>=20
> ----- Original Message -----
> From: "Magnus Hagander" <mha@sollentuna.net>
> To: "Thomas H." <me@alternize.com>
> Sent: Monday, October 30, 2006 1:21 PM
> Subject: RE: [BUGS] BUG #2712: could not fsync segment: Permission
>=20
>=20
> Yeah, IIRC it was only for the xlog stuff.
>=20
> //Magnus
>=20
> > -----Original Message-----
> > From: Thomas H. [mailto:me@alternize.com]
> > Sent: den 30 oktober 2006 13:21
> > To: Magnus Hagander
> > Subject: Re: [BUGS] BUG #2712: could not fsync segment: Permission
> >
> > the fsync error still appears:
> > 2006-10-30 13:14:52 [4896] LOG:  42501: could not fsync
> > segment 0 of relation 1663/3964774/6554576: Permission denied
> > 2006-10-30 13:14:52 [4896] LOCATION:  mdsync, md.c:785
> > 2006-10-30 13:14:52 [4896] ERROR:  XX000: storage sync failed
> > on magnetic
> > disk: Permission denied
> > 2006-10-30 13:14:52 [4896] LOCATION:  smgrsync, smgr.c:888
> >
> > the patch is for the xlog rename error / lockup, right?
> >
> > i'll try to test if the xlog lockup is fixed by the patch
> > later this evening when doing a bulk data load.
> >
> > regards,
> > thomas
> >
> > ----- Original Message -----
> > From: "Magnus Hagander" <mha@sollentuna.net>
> > To: "Thomas H." <me@alternize.com>
> > Sent: Monday, October 30, 2006 12:49 PM
> > Subject: RE: [BUGS] BUG #2712: could not fsync segment: Permission
> >
> >
> > That's permission denied. Did you by any chanc eunpack tghe=20
> EXE into a
> > different directory and then move it into place?
> >
> > Hmm. It may be in the ZIP, but isn't in the MSI. I'll talk to
> > Dave about
> > getting it out of the ZIP.
> >
> > //Magnus
> >
> >
> > > -----Original Message-----
> > > From: Thomas H. [mailto:me@alternize.com]
> > > Sent: den 30 oktober 2006 12:49
> > > To: Magnus Hagander
> > > Subject: Re: [BUGS] BUG #2712: could not fsync segment: Permission
> > >
> > > -----------------
> > > C:\Program Files\PostgreSQL\8.2beta1\bin>pg_ctl start -D
> > > D:\DB\PostgreSQL-8.2\data Server startet could not open
> > > process token: error code 5
> > > -----------------
> > >
> > > does this help?
> > >
> > > FYI: postmaster.exe still is (was) in the current beta2=20
> zip file...
> > >
> > > cheers,
> > > thomas
> > >
> > > ----- Original Message -----
> > > From: "Magnus Hagander" <mha@sollentuna.net>
> > > To: "Thomas H." <me@alternize.com>
> > > Sent: Monday, October 30, 2006 12:37 PM
> > > Subject: RE: [BUGS] BUG #2712: could not fsync segment: Permission
> > >
> > >
> > > I didn't *think* so - it should have no changes affecting
> > > that. Can you
> > > start it manually frmot he commandprmopt using pg_ctl and see
> > > if you get
> > > a different error msg on that?
> > >
> > > WRT postmaster.exe, you can just remove that file, it's not used
> > > anymore. And it's not installed by the current MSI
> > installer anymore.
> > >
> > > //Magnus
> > >
> > > > -----Original Message-----
> > > > From: Thomas H. [mailto:me@alternize.com]
> > > > Sent: den 30 oktober 2006 00:18
> > > > To: Magnus Hagander
> > > > Subject: Re: [BUGS] BUG #2712: could not fsync segment:=20
> Permission
> > > >
> > > > hmm thats what i did - b2 is running here all the time (so
> > > > pg_ctl really is v8.2b2). still, replacing didn't work. so
> > > > what i meant by build-dependent is, that the new patched
> > > > 8.2b2 postgres.exe might also need a newer pg_ctl than the
> > > > one that comes with the b2 package?
> > > >
> > > > cheers,
> > > > thomas
> > > >
> > > > ----- Original Message -----
> > > > From: "Magnus Hagander" <mha@sollentuna.net>
> > > > To: "Thomas H." <me@alternize.com>
> > > > Sent: Sunday, October 29, 2006 10:37 PM
> > > > Subject: RE: [BUGS] BUG #2712: could not fsync segment:=20
> Permission
> > > >
> > > >
> > > > Hi!
> > > >
> > > > Yeah, it might be versio ndependent. If you can, please
> > > first install
> > > > 8.2beta2 and *then* replace the files. That's the version I
> > > > patched and
> > > > used.
> > > >
> > > > //Magnus
> > > >
> > > > > -----Original Message-----
> > > > > From: Thomas H. [mailto:me@alternize.com]
> > > > > Sent: Sunday, October 29, 2006 10:35 PM
> > > > > To: Magnus Hagander
> > > > > Subject: Re: [BUGS] BUG #2712: could not fsync segment:
> > Permission
> > > > >
> > > > > hi magnus
> > > > >
> > > > > sorry for directly writing to you - don't want to bother the
> > > > > others with my noise ;-)
> > > > >
> > > > > unfortunately it cannot even start with the replaced files.
> > > > > (don't mind the service name - i updated from b1 to b2
> > > > > without changing folder/service names)
> > > > >
> > > > > -----------------
> > > > > The PostgreSQL Database Server 8.2beta1 service is starting.
> > > > > The PostgreSQL Database Server 8.2beta1 service could not
> > > > be started.
> > > > > A system error has occurred.
> > > > > System error 1067 has occurred.
> > > > > The process terminated unexpectedly.
> > > > > -----------------
> > > > >
> > > > > the eventlog says:
> > > > > pg_ctl: konnte >postgres< Programmdatei nicht finden (which
> > > > > means: "pg_ctl: could not locate >postgres< file")
> > > > >
> > > > > there are no entries in pg_log.
> > > > >
> > > > > the pgsql-8.2beta2 service is defined as:
> > > > > "C:\Program Files\PostgreSQL\8.2beta1\bin\pg_ctl.exe"
> > > > > runservice -N "pgsql-8.2beta1" -D "D:\DB\PostgreSQL-8.2\data\"
> > > > >
> > > > >
> > > > > what i've done is: replaced postgresql.exe from b2 with the
> > > > > one from your
> > > > > patch. that should be enough, right? also tried to replace
> > > > > postmaster.exe
> > > > > (which seems to be the same file), but with the same result.
> > > > >
> > > > > is pg_ctl.exe build-versions sensitive?
> > > > >
> > > > > best regards,
> > > > > thomas
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>=20
>=20
>=20