Thread: pgsqlODBC problems
Hi, I need some information regarding pgsqlODBC driver on Windows2000. We use an application which inserts records pallely into an SQL database via ODBC. It estableshes 16 pallel connections and continously inserts data. The software works well on a test environment with MS Access and MS ODBC driver. Using Postgres the application stopps inserting rows after 2-3 hours. Is there anybody who uses the postgres ODBC driver 24x7? Is that possible that the odbc dll contains a memory leak or a bug? At the time losing the connection the following entry appears in the postgres log file: ------------------------------------------------------------------- 2005-01-12 00:01:31 LOG: unexpected EOF on client connection 2005-01-12 00:01:31 LOG: could not receive data from client: No connection could be made because the target machine actively refused it. ------------------------------------------------------------------- Other question: After numerous restart of the above mentioned software there are 50-70 connections in postgres (PGAdminIII server status window). How could I set a timeout for these connections to be destroyed quicker. (Environment: Win2k, PG8RC2, pgsqlODBC 7.03.02.00) Thank you very much, -- Csaba Együd. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12.
Am 13 Jan 2005 um 13:33 hat Együd Csaba geschrieben: > Hi, > I need some information regarding pgsqlODBC driver on Windows2000. We use an > application which inserts records pallely into an SQL database via ODBC. > It estableshes 16 pallel connections and continously inserts data. The > software works well on a test environment with MS Access and MS ODBC driver. > > > Using Postgres the application stopps inserting rows after 2-3 hours. Is > there anybody who uses the postgres ODBC driver 24x7? Is that possible that > the odbc dll contains a memory leak or a bug? > > At the time losing the connection the following entry appears in the > postgres log file: > ------------------------------------------------------------------- > 2005-01-12 00:01:31 LOG: unexpected EOF on client connection > 2005-01-12 00:01:31 LOG: could not receive data from client: No > connection could be made because the target machine actively refused it. > ------------------------------------------------------------------- > Actively refused it: Seems, that the client TCP/IP stack has reached maximum open or pending close socket connections. In this state, please check, if you can create new ODBC connections to the server and see if this works. Check it with netstat -n to see a growing while the inserts. My own code shows me, that I am also would have too much open connections. A memory problem would be told by the OS and you have not given any client side log entries. > Other question: After numerous restart of the above mentioned software there > are 50-70 connections in postgres (PGAdminIII server status window). How > could I set a timeout for these connections to be destroyed quicker. > If I close my test app, my connections will be closed after a short time. > > (Environment: Win2k, PG8RC2, pgsqlODBC 7.03.02.00) > > > > Thank you very much, > > -- Csaba Együd. > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12. > > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12. > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >
thank you Lothar, I'm going to check these.
bye,
Csaba
-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of
lothar.behrens@lollisoft.de
Sent: Saturday, January 15, 2005 11:01 AM
To: Pgsql-Odbc@Postgresql.Org
Subject: Re: [ODBC] pgsqlODBC problems
Am 13 Jan 2005 um 13:33 hat Együd Csaba geschrieben:
> Hi,
> I need some information regarding pgsqlODBC driver on Windows2000. We
> use an application which inserts records pallely into an SQL database via
ODBC.
> It estableshes 16 pallel connections and continously inserts data. The
> software works well on a test environment with MS Access and MS ODBC
driver.
>
>
> Using Postgres the application stopps inserting rows after 2-3 hours.
> Is there anybody who uses the postgres ODBC driver 24x7? Is that
> possible that the odbc dll contains a memory leak or a bug?
>
> At the time losing the connection the following entry appears in the
> postgres log file:
> -------------------------------------------------------------------
> 2005-01-12 00:01:31 LOG: unexpected EOF on client connection
> 2005-01-12 00:01:31 LOG: could not receive data from client: No
> connection could be made because the target machine actively refused it.
> -------------------------------------------------------------------
>
Actively refused it: Seems, that the client TCP/IP stack has reached maximum
open or pending close socket connections.
In this state, please check, if you can create new ODBC connections to the
server and see if this works. Check it with netstat -n to see a growing
while the inserts.
My own code shows me, that I am also would have too much open connections.
A memory problem would be told by the OS and you have not given any client
side log entries.
> Other question: After numerous restart of the above mentioned software
> there are 50-70 connections in postgres (PGAdminIII server status
> window). How could I set a timeout for these connections to be destroyed
quicker.
>
If I close my test app, my connections will be closed after a short time.
>
> (Environment: Win2k, PG8RC2, pgsqlODBC 7.03.02.00)
>
>
>
> Thank you very much,
>
> -- Csaba Együd.
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12.
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 2005.01.12.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.12 - Release Date: 2005.01.14.
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.12 - Release Date: 2005.01.14.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.12 - Release Date: 2005.01.14.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.12 - Release Date: 2005.01.14.