Re: Thread configure flag

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Thread configure flag
Date: 2003-06-16 18:58:59
Message-ID: Pine.LNX.4.44.0306161932110.2751-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane writes:

> When Bruce and I discussed this last week, we assumed you'd object if
> we did not do it this way ;-). --with-threads is a feature that can't
> be supported on some platforms. Usually you argue that configure
> shouldn't auto-enable features in some places and not others.

But this isn't the same thing as supporting some external package. If
readline is missing, you install it and repeat. But if thread-safeness is
missing, there's nothing you can do. Therefore I think that the default
behavior should be to do as good as the operating system can.

Consider this: If an operating system did not support thread-safe
applications outright (do such operating systems exist?) then users would
never get the idea to write thread-safe libpq applications, so the option
to make a thread-safe libpq would be useless.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2003-06-16 18:59:22 Re: Thread configure flag
Previous Message Bruce Momjian 2003-06-16 18:10:51 Re: bug in pg.py and the fix