And I suprised that postgre will not support any of old systems like FAT32 or old os like winme.
First: it's either Postgres or PostgreSQL, it's never postgre
my qustion should I exclude any one has an old system and use postgre or not ??
Yes. I very much doubt that you'll lose a substantial number of potential customers with that restriction.
Neither FAT32 or Windows ME are suitable to run a database server (or any computer as a matter of fact)
Anyone using that (especially WinME) should upgrade. Every modern version of Windows (that means everything since Windows 2000) uses NTFS as the file system by default and for a good reason. NTFS is much more robust than FAT
- Does any client need to have postgres installed too ?
- about the connection limit I read in previous link about this problem and I am asking if that mean I will face problems if more than 125 are connected at the same time to the server.
I cannot run with more than about 125 connections at once, despite having capable hardware
When running as a service, you may experience failures with more than approximately 125 simultaneous connections. This can happen because some of the libraries that PostgreSQL is dependent on are dependent on user32.dll which allocates memory from an area known as the Desktop Heap. The desktop heap is assigned to each logon session, with non-interactive sessions typically being assigned 512KB. Each postgres process that runs typically consumes approximately 3.2KB of desktop heap, which coupled with other overhead can exhaust the allocated heap at somewhere around 125 connections. This doesn't happen when running from the command line (or more precisely, happens with much higher numbers of connections) because the interactive logon session is typically allocated 3MB of Desktop Heap.
You can increase the non-interactive Desktop Heap by modifying the third SharedSection value in the registry as described in this Microsoft Knowledgebase article. Note that this should be done with great care as specifying a value that is excessively high may prevent your system from booting.
Does any client need to have postgres installed too ?
If client in that question refers to "clients" in client/server, then no not every client must install the database server (that's what client/server is about).
If client is customer, than yes every customer than runs your software must install a server somewhere.
Originally Posted by isaac_cm
ordinary database application can run as a single user or as a client / server, in a client server mode the number of users will exceed 125 connection
Using Windows for a real database server is probably not such a good idea.
But apparently there are solutions for this problem (as described on the Wiki page) and not everybody has this problem.
But have no experience with this, so I would suggest you post this to the postgres admin mailing list.
"Before posting to a list, you may wish to search the archives.
The mailing lists are also available at the PostgreSQL news server. However, in order to post to a list, you must still subscribe to that list (but it is possible to subscribe without receiving mail)"