Re: [HACKERS] Updating column on row update - Mailing list pgsql-general

From Scott Marlowe
Subject Re: [HACKERS] Updating column on row update
Date
Msg-id dcc563d10911222132n7a5440bauecb76185272e1fd@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Updating column on row update  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Sun, Nov 22, 2009 at 10:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Part of the motivation for allowing inline blocks was to allow for
>> conditional logic.
>
> I don't think that argument really applies to this case, because the
> complaint was about not being sure if plpgsql is installed.  If it
> isn't, you can hardly use a plpgsql DO block to fix it.
>
> (Is anyone up for revisiting the perennial topic of whether to install
> plpgsql by default?  Andrew's argument does suggest that DO might offer
> a new consideration in that tradeoff.)

One non-coding vote for yes.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Updating column on row update
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Updating column on row update