Re: [GENERAL] Updating column on row update - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] Updating column on row update
Date
Msg-id 23894.1258953554@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Updating column on row update  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [GENERAL] Updating column on row update  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: [GENERAL] Updating column on row update  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-hackers
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.)

            regards, tom lane

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [GENERAL] Updating column on row update
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff