On Dec 9 23:40, Reini Urban wrote:
Corinna just answered to this problem, which I suspected to be a
cygserver problem, but she said that the caller is responsible for
allocating the msg buffer, so it should be a postgresql problem.
I'm still scratching my head also, because I'm not really
Hi all,
once again I've hosed my PostgreSQL installation. I've more or less accidentally
upgraded PostgreSQL to the latest version and it would start no more. I've
perused the archives and collected all remedies I've found. Most notably:
- I had fixed the / and /bin permissions previously and
Markus Hoenicka schrieb:
once again I've hosed my PostgreSQL installation. I've more or less
accidentally
upgraded PostgreSQL to the latest version and it would start no more. I've
perused the archives and collected all remedies I've found. Most notably:
- I had fixed the / and /bin permissions
Reini Urban [EMAIL PROTECTED] was heard to say:
The cause is that the internal cygserver msg buffer is allocated
read-only. (IsBadWritePtr() fails)
Reason unknown. gcc? cygwin?
Solution pending.
Szteps to reproduce:
cygserver
ipcs
= Bad system call
Oh great. I'm afraid fixing this is
Markus Hoenicka schrieb:
Reini Urban [EMAIL PROTECTED] was heard to say:
The cause is that the internal cygserver msg buffer is allocated
read-only. (IsBadWritePtr() fails)
Reason unknown. gcc? cygwin?
Solution pending.
Szteps to reproduce:
cygserver
ipcs
= Bad system call
Oh great. I'm afraid
5 matches
Mail list logo