| From: | Philip Yarra <philip(at)utiba(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Dann Corbit <DCorbit(at)connx(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, Larry Rosenman <ler(at)lerctr(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Thread-safe configuration option appears to |
| Date: | 2003-08-07 00:13:02 |
| Message-ID: | 200308071013.02562.philip@utiba.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 7 Aug 2003 09:49 am, Tom Lane wrote:
> People
> running on such a platform are certainly not going to care whether libpq
> is thread-safe or not.
Precisely. If your application on that platform can't start multiple threads
of execution, it's a moot point whether the DB interface on that platform is
thread-safe. It'll never get multiple threads running through it anyway.
Regards, Philip Yarra.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-08-07 01:33:12 | encoding question |
| Previous Message | Tom Lane | 2003-08-07 00:05:13 | Re: v7.4 Beta 1 fails regression on Digital Unix/Tru64 4.0 |