Re: Question About PostgreSQL Extensibility

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: felix(dot)quintgz(at)yahoo(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Question About PostgreSQL Extensibility
Date: 2023-10-17 09:52:51
Message-ID: CAKt_Zft8P2wPKpR81nNwaYA-B1G-9=J1bgt_Y1_uN7zrTRjSkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 16, 2023 at 10:59 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Fri, 2023-10-13 at 13:55 +0000, felix(dot)quintgz(at)yahoo(dot)com wrote:
> > For the same reason that you can use python or perl in postgresql. It's
> just another language.
> > I have .net code running on several sql servers and to change the
> database to postgresql I have to reprogram them.
>
> Yes, you'll have to rewrite them.
>

Or pick up the pldotnet handler and patch it to work on the new version.
My experience forward porting such things is that it is usually trivial.

Of course there may be other reasons to rewrite but it really depends on a
lot of factors.

>
> Yours,
> Laurenz Albe
>
>
>

--
Best Wishes,
Chris Travers

Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2023-10-17 13:39:35 Re: PITR partial timing
Previous Message Ron 2023-10-16 21:06:44 Re: Understanding max_locks_per_transaction