Skip site navigation (1) Skip section navigation (2)

Re: contrib function naming, and upgrade issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: contrib function naming, and upgrade issues
Date: 2009-03-23 23:10:32
Message-ID: 4635.1237849832@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>  Tom> A defining SQL script is the way to go.

> But I disagree with this, for the simple reason that we don't have
> anything like enough flexibility in the form of conditional DDL or
> error handling, when working in pure SQL without any procedural help.

So?  You can have the script create, execute, and remove a function,
and thereby perform any operation that a function could possibly
perform for you.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Greg SmithDate: 2009-03-23 23:15:35
Subject: Resetting cluster-wide statistics
Previous:From: Jeff DavisDate: 2009-03-23 22:59:45
Subject: Re: GIN fast-insert vs autovacuum scheduling

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group