problem with windows xp sp2 and postgres-8.1.3

Поиск
Список
Период
Сортировка
От Istvan Nagy
Тема problem with windows xp sp2 and postgres-8.1.3
Дата
Msg-id 000c01c63b74$67bb2180$6402a8c0@b2b4u.hu
обсуждение исходный текст
Список pgsql-general
Hello Guys,
 
first of all, great effort from you this tool.
 
Problem exists with following config:
- Windows XP Pro, SP2 (English).
- PostgreSQL-8.1.3
- lot of development programs, and IDE-s (for the clients i am working unfortunately
they are windoz-based :-(...).
 
Same problem occurs as described here
and here.
 
Could you have an assist?
Magnus (Magnus Hagander), would you have any idea about it?
 
Problem description:
When starting the service: the following error occurs(can be read from  Application Event):
=========================================================
"could not create inherited socket: error code 10022".
=========================================================
 
As i tried again manually(postmaster...), had the same problem. I turned off my firewall services,
windows security center firewall and antivirus check (automatic updates are on),
but i got the same error.
Ok, deleted the postgres, deleted the user, deleted registry settings for postgres. Reinstalled
and tried to make it run. Unfortunately the same error happened.
 
It is a windows-based network address bind problem, described below:
=========================================================
WSAEINVAL 10022
Invalid argument
Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt
function). In some instances, it also refers to the current state of the socket—for instance,
calling accept on a socket that is not listening.
Header
Declared in Winsock2.h
=========================================================
Thanks, m$ guys, was really helpful. :-(
 
The problem exists since i upgraded (unfortunately i had to, not wanted) from XP-SP1
to XP-SP2. Before that it was Postgres-8.0.4 installed, worked fine, seemed really
cool. BUT, times and development environment (and os-s) are changing. :-(
 
Can it have anything related to windows-socket bind problems with Windows-XP-SP2
integrated firewalls however it is disabled?
 
Thanks in advance,
 István
 
 
Вложения

В списке pgsql-general по дате отправления:

Предыдущее
От: CG
Дата:
Сообщение: Re: ltree + gist index performance degrades significantly over a night
Следующее
От: Stephan Szabo
Дата:
Сообщение: Re: Wish: remove ancient constructs from Postgres