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 ...
So you could REPLACE an existing extension and add whatever you need to.
In response to
pgsql-hackers by date
|Next:||From: Greg Sabino Mullane||Date: 2009-03-23 12:41:43|
|Subject: Re: Have \d show child tables that inherit from the specified parent|
|Previous:||From: Nikhil Sontakke||Date: 2009-03-23 11:39:18|
|Subject: Re: Partitioning feature ...|