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

Re: contrib function naming, and upgrade issues

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Subject: Re: contrib function naming, and upgrade issues
Date: 2009-03-23 11:46:52
Message-ID: 200903231246.54628.dfontaine@hi-media.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Monday 23 March 2009 12:34:31 Robert Haas wrote:
> That might not be the only time you ever want to create dependencies
> on the module object.  What if the module wants to create an
> additional table, view, etc. at some later time, following the load?
> I'm not sure whether there's a use case for that, but it doesn't seem
> totally implausible.

Then there's Tom's idea of SET module TO ...; to have the context handy, or a 
WIP syntax in http://wiki.postgresql.org/wiki/ExtensionPackaging

  CREATE OR REPLACE EXTENSION foo ...
  AS $$
  $$;

So you could REPLACE an existing extension and add whatever you need to.
-- 
dim

In response to

Responses

pgsql-hackers by date

Next:From: Greg Sabino MullaneDate: 2009-03-23 12:41:43
Subject: Re: Have \d show child tables that inherit from the specified parent
Previous:From: Nikhil SontakkeDate: 2009-03-23 11:39:18
Subject: Re: Partitioning feature ...

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