Re: PL/pgSQL 2

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Joel Jacobson <joel(at)trustly(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(at)joh(dot)to>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/pgSQL 2
Date: 2014-09-02 20:12:53
Message-ID: 20140902201253.GK19338@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 2, 2014 at 07:06:02PM +0200, Joel Jacobson wrote:
> On Tue, Sep 2, 2014 at 7:01 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > On Tue, Sep 2, 2014 at 06:57:42PM +0200, Joel Jacobson wrote:
> >> On Tue, Sep 2, 2014 at 6:45 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> > SINGLETON UPDATE ...?
> >>
> >> Does it come with built-in spell check? :-) It's a bit long to write.
> >> I like STRICT, that maps good to what we already have with SELECT ...
> >> INTO STRICT.
> >
> > Spell checker coming in plpgsql3! ;-)
> >
> > Anyway, as you have seen, the problem is not creating plpgsql2 --- you
> > could do that yourself on your own and distribute it. What you want is
> > for the community to develop/maintain it, and as you have also seen,
> > everyone uses plpgsql slightly differently, so if you want the community
> > to maintain it, you are only going to get some of the things you want.
>
> Very true, I totally agree.
>
> But what do you think about,
> STRICT UPDATE ...?

Seems fine to me.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-09-02 20:15:30 Re: Scaling shared buffer eviction
Previous Message Robert Haas 2014-09-02 19:22:48 Re: B-Tree support function number 3 (strxfrm() optimization)