| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Thomas Hallgren <thomas(at)tada(dot)se> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remote PL/Java, Summary |
| Date: | 2006-04-01 13:24:44 |
| Message-ID: | 442E7F1C.6020607@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
> We already do use threads on Windows to a limited extent to do things
> like timers and pseudo-signal handling.
>
> If this were a greenfields project then your arguments would have
> force. But for how long would you like to suspend Postgres development
> activity while we re-implement everything in Java? Not to mention the
> effort to recruit new developers to replace those who leave because
> they can't or don't want to be part of the effort.
>
> For better or worse, PostgreSQL is written in C, and I can't see that
> changing.
>
> It might be interesting to take a frozen code base for PostgreSQL and
> reimplement it in Java, and then run some comparisons, both for
> performance and crash stability. I just counted roughly 100k lines of
> source code, so a reimplementation effort would be distinctly
> non-trivial.
>
and a happy April 1 to you too, btw.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jeroen van iddekinge | 2006-04-01 13:40:19 | Postgres dies when using an intarray operator |
| Previous Message | Andrew Dunstan | 2006-04-01 13:13:01 | Re: Remote PL/Java, Summary |