From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Atul Chojar <achojar(at)airfacts(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to automatically propagate new/changed database functions from one database to another |
Date: | 2009-06-05 17:36:50 |
Message-ID: | 1244223410.12929.27.camel@jd-laptop.pragmaticzealot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Fri, 2009-06-05 at 13:12 -0400, Atul Chojar wrote:
> We want to implement a mechanism by which if any database function is
> created or modified in one database, then the same should
> automatically get done in another (1 or more) database(s).
>
>
>
> It seems triggers on system catalogs like pg_proc are not allowed. Is
> there any way in postgres to do this, by some other way?
This is the wrong away to go about it. You should put this into your
development process not within the database itself. There are a number
of utilities that would allow you to do such a thing.
Joshua D. Drake
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
From | Date | Subject | |
---|---|---|---|
Next Message | Lewis Kapell | 2009-06-05 17:49:06 | Re: Postgres has stopped logging |
Previous Message | Atul Chojar | 2009-06-05 17:12:15 | How to automatically propagate new/changed database functions from one database to another |
From | Date | Subject | |
---|---|---|---|
Next Message | David | 2009-06-05 17:44:31 | Re: maintaining referential integrity |
Previous Message | Louis Lam | 2009-06-05 17:31:18 | Re: catalog view use to find DATABASE, LANGUAGE, TABLESPACE, SCHEMA, SEQUENCE privileges granted to user or role |