Re: Patch: plan invalidation vs stored procedures

From: Decibel! <decibel(at)decibel(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Asko Oja <ascoja(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Joshua Drake <jd(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>, Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>
Subject: Re: Patch: plan invalidation vs stored procedures
Date: 2008-08-22 04:14:04
Message-ID: 2AC7CAF8-72B1-49B6-B10D-46289B0D32F3@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Aug 20, 2008, at 9:18 AM, Tom Lane wrote:
> However I have no hard evidence to back up drawing the line there
> rather
> than somewhere else. Anyone have data on what sort of DDL changes are
> common in their applications?

I've worked in environments where we used stored functions
extensively and where we didn't. Table DDL is generally fairly common
in both cases, and if stored functions or views are used, it's very
common for table DDL to trigger updates in views and functions. It's
fairly common to have to update just functions to kill bugs or change
functionality. Trigger changes are a bit less frequent, and views are
probably the least frequent.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Decibel! 2008-08-22 04:28:48 Re: Improving non-joinable EXISTS subqueries
Previous Message D'Arcy J.M. Cain 2008-08-22 03:18:24 Re: Proposal: new border setting in psql