Re: PgSQL: Want opinions, experiences and tips

From: Saravanan Bellan <SBellan(at)jareva(dot)com>
To: Saravanan Bellan <SBellan(at)jareva(dot)com>, pgsql-cygwin(at)postgresql(dot)org
Subject: Re: PgSQL: Want opinions, experiences and tips
Date: 2002-09-03 18:30:39
Message-ID: A37D6E7E941A1E498B4B98F3E4AFA9208973B3@MAIL.design2deploy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-cygwin

So I guess from jason's recent post, this
http://sources.redhat.com/ml/cygwin/2000-04/msg00267.html
<http://sources.redhat.com/ml/cygwin/2000-04/msg00267.html> is the answer
to my question.

I'm also copying the posting here,

From: DJ Delorie <dj at delorie dot com>

Open regedit (or regedt32) and find the key
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\

Create a new DWORD value there called "heap_chunk_in_mb" that contains
the maximum amount of memory (in Mb) your application needs (watch the
hex/decimal toggle). Exit and restart all cygwin applications.

The default is 128 (i.e. 128Mb) if no registry key is set.

Here is a more interesting "max memory" program:

main()
{
unsigned int bit=0x40000000, sum=0;
char *x;

while (bit > 4096) {
x = malloc(bit);
if (x)
sum += bit;
bit >>= 1;
}
printf("%08x bytes (%.1fMb)\n", sum, sum/1024.0/1024.0);

return 0;
}

-----Original Message-----
From: Saravanan Bellan [mailto:SBellan(at)jareva(dot)com]
Sent: Monday, July 22, 2002 5:07 PM
To: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: [CYGWIN] PgSQL: Want opinions, experiences and tips

>>and also you have to add a line to the registry if you want to use a lot
of memory.

What is the line to be added in the registry?

-----Original Message-----
From: Henshall, Stuart - WCP
[mailto:SHenshall(at)westcountrypublications(dot)co(dot)uk]
Sent: Monday, July 22, 2002 6:54 AM
To: 'Nikhil G. Daddikar'; pgsql-cygwin(at)postgresql(dot)org
Subject: Re: [CYGWIN] PgSQL: Want opinions, experiences and tips

I've had good results with it. The only bit that I have noticed to be slower
is the intial connection as cygwin actually copies everything when it forks.
There is also the 63 Process limit which will limit the number of
similtaneus connections, and also you have to add a line to the registry if
you want to use a lot of memory. You will also need to download cygipc as
well as the main cygwin distribution.

hth,
- Stuart

> -----Original Message-----
> From: Nikhil G. Daddikar [ mailto:ngd(at)celoxis(dot)com <mailto:ngd(at)celoxis(dot)com>
]
> Sent: 20 July 2002 11:50
> To: pgsql-cygwin(at)postgresql(dot)org
> Subject: [CYGWIN] PgSQL: Want opinions, experiences and tips
>
>
> Hi,
>
> We've been using PgSQL 7.1.3 on Linux on our ASP production
> system and are extremely happy with everything so far. We are
> now thinking of giving windows versions of our application
> for in-house installations (around 50 users).
>
> We were thinking of using Cygwin as that would not only give
> us to re-use our unix scripts but also because it's ported
> pgsql 7.2.1 (the latest version). Also, it's installation is
> quite simple for end users.
>
> Is this a good idea?
>
> Is cygwin pgsql 7.2.1 "stable"? Is it slower compared to
> unix? If so by how much?
>
> Any experiences or help is greatly appreciated.
>
> Thanks.
> Nikhil
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

Responses

Browse pgsql-cygwin by date

  From Date Subject
Next Message Jason Tishler 2002-09-03 20:29:40 Re: PgSQL: Want opinions, experiences and tips
Previous Message Jason Tishler 2002-09-03 16:57:18 Re: PostgreSQL unsuitable for large datasets?