Re: idea, proposal: only preloadable libraries (conditional load)

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Greg Stark <stark(at)enterprisedb(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: idea, proposal: only preloadable libraries (conditional load)
Date: 2009-03-11 14:18:43
Message-ID: 1236781123.28644.133.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Wed, 2009-03-11 at 13:14 +0000, Greg Stark wrote:
> On Wed, Mar 11, 2009 at 12:56 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> >
> > In the longer term it will be very useful to have the ability to support
> > multiple language variants, including older PostgreSQL syntax to allow
> > legacy systems to work with Postgres at the same time as allowing new
> > development to continue.
>
>
> So I think having multiple parsers for different versions of Pg
> backwards compatibility is an awful idea.

There are a number of people interested in producing open source
compatibility layers. I realise you may not be one of them, but that's
no reason to stop the idea from taking root.

> It would be a huge
> maintenance headache since every time we change a structure that the
> parser works someone would have to maintain all those compatibility
> parsers.

If it's a plugin that "someone" isn't any concern of ours. External
projects can keep up with releases, or specific customer implementations
may simply choose to standardise on one release and go with that.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2009-03-11 14:41:40 Re: Prepping to break every past release...
Previous Message Pavel Stehule 2009-03-11 14:15:03 Re: idea, proposal: only preloadable libraries (conditional load)