| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Duane Currie <dcurrie(at)sandman(dot)acadiau(dot)ca>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Threads |
| Date: | 1999-08-03 15:13:11 |
| Message-ID: | Pine.BSF.4.10.9908031212440.27315-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 3 Aug 1999, Tom Lane wrote:
> Duane Currie <dcurrie(at)sandman(dot)acadiau(dot)ca> writes:
> > Would it not be advantageous to use threading in the PostgreSQL backend?
>
> Just so you don't break the code for non-threaded platforms.
>
> I believe mysql *requires* working thread support, which is one reason
> it is not so portable as Postgres... we should not give up that advantage.
Just curious here, but out of all the platforms we support, are there any
remaining that don't support threads?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adriaan Joubert | 1999-08-03 15:15:15 | ERROR: btree scan list trashed ?? |
| Previous Message | Tom Lane | 1999-08-03 15:12:23 | Re: bad select performance fixed by forbidding hash joins |