Thread: PostgreSQL 8.0.2 and 7.4.7 does not work anymore since cygwin 1.5.14
Hello! I used a self compiled PostgreSQL 8.0.2 under cygwin. Since the update from cygwin 1.5.13 to 1.5.16 the postmaster process always crashes with Signal 12, bad system call. Recompiling did not change that. With PostgreSQL 7.4.7 I lost the posibility to connect to the database with psql and the other command line tools like vacuumdb. A connection worked only for a few moments after a restart of the postmaster. The command line tools suggested, that the database was not running. But a connection with the JDBC-driver still worked. I changed back to 1.5.13, but the crashes on PostgreSQL 8.0.2 are still there. But for PostgreSQL 7.4.7 the command line tools got a connection again without a restart of the postmaster. Could anyone verify this behaviour or has further suggestions? I did not find any information on the cygwin or postgresql mailinglist-archives yet. A great problem on my side is, that i cannot send emails greater than 5 kb. Regards, Roland. -- Roland Walter MOSAIC SOFTWARE AG Telefon: 02225/882-411 Fax: 02225/882-201 http://www.mosaic-ag.com
Roland Walter schrieb: > I used a self compiled PostgreSQL 8.0.2 under cygwin. Since > the update from cygwin 1.5.13 to 1.5.16 the postmaster > process always crashes with Signal 12, bad system call. Recompiling > did not change that. Confirmed and discussed in this and in the cygwin mailing list. IPC fails with isBadWritePtr on the first postgresql provided shmem area. (within cygserver) No fix yet. But a lot of people can run without this problem, only a few systems are affected. I see no pattern yet why. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ http://phpwiki.org/
Ok, problem solved for PostgreSQL 8.0.x. Was my fault. Must have deleted the line export CYGWIN in .bashrc of database user. So the database did not see that CYGWIN was set to 'ntsec server'. But the problems with PostgreSQL 7.4.7+ still remains with cygwin 1.5.14 to 1.5.16. A few moments after the start of the postmaster command line tools like psql or vacuumdb think there is no database, but Java-applications with JDBC are still able to connect. Regards, Roland. -- Roland Walter MOSAIC SOFTWARE AG Telefon: 02225/882-411 Fax: 02225/882-201 http://www.mosaic-ag.com
Roland,
On Tue, May 17, 2005 at 01:51:03PM +0200, Roland Walter wrote:
> But the problems with PostgreSQL 7.4.7+ still remains with cygwin
> 1.5.14 to 1.5.16. A few moments after the start of the postmaster
> command line tools like psql or vacuumdb think there is no database,
> but Java-applications with JDBC are still able to connect.
Should be solved in Cygwin 1.5.17 -- try a snapshot to make sure. See
the following Cygwin mailing list thread for the details, if interested:
http://cygwin.com/ml/cygwin/2005-05/msg00076.html
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Jason Tishler <jason@tishler.net> writes: > Roland, > > On Tue, May 17, 2005 at 01:51:03PM +0200, Roland Walter wrote: >> But the problems with PostgreSQL 7.4.7+ still remains with cygwin >> 1.5.14 to 1.5.16. A few moments after the start of the postmaster >> command line tools like psql or vacuumdb think there is no database, >> but Java-applications with JDBC are still able to connect. > > Should be solved in Cygwin 1.5.17 -- try a snapshot to make sure. See > the following Cygwin mailing list thread for the details, if interested: > > http://cygwin.com/ml/cygwin/2005-05/msg00076.html > I tried the snapshot from 2005-05-17 and the problem is solved. Thank you. -- Roland Walter mailto: rwa (at) mosaic-ag (dot) com MOSAIC SOFTWARE AG phone: +49 (0) 22 25 / 88 2-41 1 Am Pannacker 3 fax: +49 (0) 22 25 / 88 2-20 1 D-53340 Meckenheim http://www.mosaic-ag.com