pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Gary Doades <gpd@gpdnet.co.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL vs. Oracle vs. Microsoft
Date: Tue, 11 Jan 2005 07:37:21 +0000
Message-ID: <41E38231.5090301@gpdnet.co.uk> (raw )
In-Reply-To: <41E31815.4030908@fastcrypt.com >
References: <Xns95D671D321E39rr8xca@200.46.204.72 >
<41E22F04.103@gpdnet.co.uk >
<33c6269f05011008074b33b812@mail.gmail.com >
<20050110173307.GA18357@zong.spline.inf.fu-berlin.de >
<20050110114200.76e9a51d.frank@wiles.org >
<33c6269f050110094646897c3e@mail.gmail.com >
<opskekwnc9cq72hf@musicbox >
<41E2E19D.1000903@gpdnet.co.uk >
<opskel22vzcq72hf@musicbox >
<41E2F43C.5020702@fastcrypt.com >
<41E2F9ED.1070206@gpdnet.co.uk >
<41E31815.4030908@fastcrypt.com >
Dave Cramer wrote:
> Ok, so one use case is to select a large number of rows and do some
> non-trivial operation on them.
> I can see where getting the rows inside the server process ( ie some
> procedural language ) thereby reducing the round trip overhead would be
> beneficial. However how do you deal with the lack of control ? For
> instance what happens if you run out of memory while doing this ? I'm
> not sure about other DB'S but if you crash the procedural language
> inside postgres you will bring the server down.
>
> It would seem to me that any non-trivial operation would be better
> handled outside the server process, even if it costs you the round trip.
Since a .NET language is operating effectively inside a VM it is pretty
much impossible to bring down the server that way. Only a bug in the
.NET runtime itself will do that. The C# try/catch/finally with .NET
global execption last chance handlers will ensure the server and your
code is well protected.
Cheers,
Gary.
view thread (46+ messages) latest in thread
Message-ID: <41E38231.5090301@gpdnet.co.uk>
Permalink: ../41E38231.5090301@gpdnet.co.uk/
Also on: postgresql.org/message-id/41E38231.5090301@gpdnet.co.uk
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gpd@gpdnet.co.uk
Subject: Re: PostgreSQL vs. Oracle vs. Microsoft
In-Reply-To: <41E38231.5090301@gpdnet.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox