Re: big text field -> message type 0x44

From: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, 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 15:44:22
Message-ID: 15855.29782.56462.833796@kelvin.csl.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

You'll probably find Tomas's code breaks on Linux too...

Lee.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dan Langille 2002-12-05 16:02:00 7.4 - TODO : alter table drop foreign key
Previous Message Tomas Berndtsson 2002-12-05 15:38:49 Re: big text field -> message type 0x44