From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Fernando Schapachnik <fernando(at)mecon(dot)gov(dot)ar> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: libpq usage in Samba |
Date: | 2005-03-30 15:01:54 |
Message-ID: | 87u0mtp47x.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Fernando Schapachnik <fernando(at)mecon(dot)gov(dot)ar> writes:
> I'm trying to figure out why Samba is failing at high loads if using
> Postgres as a backend (7.3.9 in my setup). On startup in makes one
> connection only against the database which is shared among all the
> Samba processes. In turn, each issue a PQexec() over the same
> connection (a SELECT, actually). Is that a safe use? I would think
> it is not, but not really sure. I mean, does libpq multiplex queries
> and handle concurrency correctly in a such a scenario?
No, it doesn't. You need to figure out a way to have each Samba
process open its own connection.
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-03-30 15:09:28 | Re: Upgrade data |
Previous Message | Sean Davis | 2005-03-30 15:01:10 | Re: plperl doesn't release memory |