Message-ID: <40ED4DE5.7020807@netcabo.pt>
Date: Thu, 08 Jul 2004 14:36:37 +0100
From: "Pedro B." <pedro.borracha@netcabo.pt>
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Newbie (to postgres) question
References: 
 <77ED2BF75D59D1439F90412CC5B109740E8A2E38@ie10-sahara.hiso.honeywell.com>
	<40EBD891.3050205@archonet.com>
	<005801c464dd$72b5bec0$0403a8c0@fejleszt4>
In-Reply-To: <005801c464dd$72b5bec0$0403a8c0@fejleszt4>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hello all,

First of all, accept my apologies for what is surely a dumb question, 
and yes i have been reading extensively through all the documents, but i 
really need to ask this.. :)

I have recently started the migration of a large ex-MySql database to 
postgresql, and im still "adapting" to the new tweaks of this new (to 
me) environment.

My question is basically... how does postgresql deal with the equivalent 
of "permanent connections of mysql"?
Alongside with the database, i have an extensive amount of .c code that 
used to just reuse sockets if they were already in an open state (and 
only if needed new one(s) would be open). It's an application that will 
run as a standalone, but many times per minute, so the reusage is indeed 
a must for me.

I have substituted the "mysql_ping"s with PQconnectPolls just to see if 
the behaviour would be alike, and right now that seems to work, but i'm 
in a standstill regarding the sockets and permanent connection usage.

Any help/directions someone might give me will be deeply appreciated.

Regards,
\\pb