Thread: libpq usage in Samba

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?

Thanks.


Fernando.

Fernando Schapachnik <fernando@mecon.gov.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