Skip site navigation (1) Skip section navigation (2)

BUG #2442: Problemas accessing DB in a multithread pross

From: "Carmen" <carmenlucia(at)globo(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2442: Problemas accessing DB in a multithread pross
Date: 2006-05-17 11:37:55
Message-ID: 200605171137.k4HBbtrL000742@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2442
Logged by:          Carmen
Email address:      carmenlucia(at)globo(dot)com
PostgreSQL version: 8.0
Operating system:   FreeBSD
Description:        Problemas accessing DB in a multithread pross
Details: 

I have a Windows system accesing a FreeBSD PostGres 8.0.
I have a multihread process in Windows using a PostGres 8.0 FreeBSD. Each
thread of this process has a TCP communicaction with a remote client and it
updates a common BD of the global process. 
TEach time two threads access a SQL API at the axact sametiem, the
process(not just the thread) is aborted. I resolved this problem defining a
critical section for each API SQL acess, but it has been causing a great
delay in my realtime program.
This problema happens, even if my BD is a local Windows PostGres.
This Windows program was migrated from Linux. Linux uses fork for each
remote client, and I dont have this kind of problem with fork. 
So, why have I this problem with threads. Is this a limitation? 
I must solve this problem to put it in production. The critical_section has
not been a godd soluction. Can you help me?

Responses

pgsql-bugs by date

Next:From: Cristiano DuarteDate: 2006-05-17 14:19:01
Subject: Re: [BUGS] BUG #2429: Explain does not report object's schema
Previous:From: Arjen van der MeijdenDate: 2006-05-17 10:31:35
Subject: BUG #2441: All useable indexes for an IN are used, not just one

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group