Re: All Production releases of PostgreSQL hung because of

There is currently no production release of PostgreSQL that runs more than 5 concurrent sessions
in Windows because the releases available for Cygwin, 7.4.3 to 7.4.5 are built with Cygserver
which has a bug that have PostgreSQL hung with more than 5 concurrent connections.

I am planning to revert to PostgreSQL 7.1 which is the latest cygwin package built with cygipc
(instead of cygserver).

It would be nice to have the latest releases of PostgreSQL rebuilt with cygipc and available
as cygwin packages.

Thanks
Jean-Pierre Pelletier

FYI, I made and I run a 7.3.5 version
with Cygserver (and Tcl) on NT4 & W2K.
I don't have any trouble with the number of sessions.
I can see up to ten postgres.exe in task manager.

--- Jean-Pierre Pelletier wrote:

> There is currently no production release of
> PostgreSQL that runs more than 5 concurrent sessions
> in Windows because the releases available for
> Cygwin, 7.4.3 to 7.4.5 are built with Cygserver
> which has a bug that have PostgreSQL hung with more
> than 5 concurrent connections.
>
> I am planning to revert to PostgreSQL 7.1 which is
> the latest cygwin package built with cygipc
> (instead of cygserver).
>
> It would be nice to have the latest releases of
> PostgreSQL rebuilt with cygipc and available
> as cygwin packages.

__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

Jean-Pierre Pelletier schrieb:
> There is currently no production release of PostgreSQL that runs more
> than 5 concurrent sessions
> in Windows because the releases available for Cygwin, 7.4.3 to 7.4.5 are
> built with Cygserver
> which has a bug that have PostgreSQL hung with more than 5 concurrent
> connections.

Hmm, that would explain the crash at the parallel_schedule regression
suite. ipcs showed 5 semaphores, and one shm, when postmaster crashed.
serial tests do work fine. max_connections=100 also works fine.

Do you have any link where this is discussed/analyzed?

> I am planning to ;revert to PostgreSQL 7.1 which is the latest cygwin
> package built with cygipc (instead of cygserver).
> ;
> It would be nice to have the latest releases of PostgreSQL rebuilt with
> cygipc and available as cygwin packages.

No problem.
If it's really a buggy cygserver I'll do a interim cygipc version.
I already had one, but it clashed with cygserver.

But I really want to try to debug cygserver then.

--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Hi.

I have postgreSQL version 7.2.1 /w cygwin running fine with more than 5
concurrent connections.
Normal 7.2.1 distro. Tested up to 12.

BTW: postgresql-cygwin cannot handle more than 62 concurrent client
connections due to a limitation in windows,
no matter what postgresql.conf says.

Greetings, Joek

-----Oorspronkelijk bericht-----
Van: pgsql-cygwin-owner(at)postgresql(dot)org
[mailto:pgsql-cygwin-owner(at)postgresql(dot)org] Namens Reini Urban
Verzonden: zaterdag 11 september 2004 11:43
Aan: cygwin
CC: pgsql-cygwin(at)postgresql(dot)org
Onderwerp: Re: [CYGWIN] All Production releases of PostgreSQL hung because
of

Jean-Pierre Pelletier schrieb:
> There is currently no production release of PostgreSQL that runs more
> than 5 concurrent sessions
> in Windows because the releases available for Cygwin, 7.4.3 to 7.4.5 are
> built with Cygserver
> which has a bug that have PostgreSQL hung with more than 5 concurrent
> connections.

Hmm, that would explain the crash at the parallel_schedule regression
suite. ipcs showed 5 semaphores, and one shm, when postmaster crashed.
serial tests do work fine. max_connections=100 also works fine.

Do you have any link where this is discussed/analyzed?

> I am planning to ;revert to PostgreSQL 7.1 which is the latest cygwin
> package built with cygipc (instead of cygserver).
> ;
> It would be nice to have the latest releases of PostgreSQL rebuilt with
> cygipc and available as cygwin packages.

No problem.
If it's really a buggy cygserver I'll do a interim cygipc version. I already
had one, but it clashed with cygserver.

But I really want to try to debug cygserver then.

--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Joek,

On Mon, Sep 13, 2004 at 10:28:39AM +0200, J. Hondius wrote:
> BTW: postgresql-cygwin cannot handle more than 62 concurrent client
> connections due to a limitation in windows,

This is really more of a Cygwin (fork) limitation than a Windows one:

http://cygwin.com/ml/cygwin/2004-09/msg00405.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