Re: big text field -> message type 0x44

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Tomas Berndtsson <tomas(at)nocrew(dot)org>
Subject: Re: big text field -> message type 0x44
Date: 2002-12-05 16:16:13
Message-ID: m3adjka1bm.fsf@varsoon.wireboard.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Lee Kindness <lkindness(at)csl(dot)co(dot)uk> writes:

> Tom Lane writes:
> > Okay, so it seems -D_REENTRANT is the appropriate fix.
> >
> > We could either add that to the template/solaris file, or just add a
> > note to FAQ_Solaris advising that it be added to the configure switches
> > if people intend to use libpq in threaded programs. Is there any
> > cost or downside to just adding it always in template/solaris?
>
> However, _REENTRANT is not a Solarisism... On all (recent) UNIX
> systems it toggles on correct handling for thread specific instances
> of historically global variables (eg errno). It should be considered
> for all platforms if libpq is intended to be used from threaded
> programs.

I know libpq is "officially" non-threadsafe, but is there anything in
there that would actually cause a problem, assuming either a
connection per thread or proper locking on the application's part?
Most of the data in the library seems to be per-connection...

-Doug

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2002-12-05 16:20:37 Re: 7.4 - TODO : alter table drop foreign key
Previous Message Dan Langille 2002-12-05 16:02:00 7.4 - TODO : alter table drop foreign key