Re: Remote PL/Java, Summary - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Remote PL/Java, Summary
Date
Msg-id 442E7F1C.6020607@dunslane.net
Whole thread Raw
In response to Re: Remote PL/Java, Summary  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Remote PL/Java, Summary  (Thomas Hallgren <thomas@tada.se>)
List 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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Remote PL/Java, Summary
Next
From: jeroen van iddekinge
Date:
Subject: Postgres dies when using an intarray operator