Re: libpq is not thread safe

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: libpq is not thread safe
Date: 2009-05-29 11:52:29
Message-ID: 1243597949.1301.7.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Bruce Momjian píše v čt 28. 05. 2009 v 17:20 -0400:

> >
> > Done, patch attached and applied.
>
> I went with a <warning> because it seemed most appropriate, but it looks
> very large:
>
> http://developer.postgresql.org/pgdocs/postgres/libpq-connect.html
>
> Should it be a notice?

I prefer warning. It is important message and beginners usually don't
know it.

Zdenek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Field 2009-05-29 11:59:21 Re: plperl error format vs plpgsql error format vs pgTAP
Previous Message David Blewett 2009-05-29 11:47:16 Re: Python 3.0 does not work with PL/Python