| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Thom Brown <thombrown(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Updating column on row update |
| Date: | 2009-11-23 05:19:14 |
| Message-ID: | 23894.1258953554@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-11-23 05:32:45 | Re: [HACKERS] Updating column on row update |
| Previous Message | Andrew Dunstan | 2009-11-23 05:05:22 | Re: [HACKERS] Updating column on row update |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-11-23 05:26:42 | Re: pgsql: Remove -w (--ignore-all-space) option from pg_regress's diff |
| Previous Message | Andrew Dunstan | 2009-11-23 05:05:22 | Re: [HACKERS] Updating column on row update |