Re: How to automatically propagate new/changed database functions from one database to another - Mailing list pgsql-general

From Atul Chojar
Subject Re: How to automatically propagate new/changed database functions from one database to another
Date
Msg-id 004701c9e622$f9eac900$edc05b00$@com
Whole thread Raw
In response to Re: How to automatically propagate new/changed database functions from one database to another  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
Could you give some examples of such utilities?

Thanks!
atul





-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Joshua D. Drake
Sent: Friday, June 05, 2009 1:37 PM
To: Atul Chojar
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] How to automatically propagate new/changed database
functions from one database to another

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@jabber.postgresql.org
   Consulting, Development, Support, Training
   503-667-4564 - http://www.commandprompt.com/
   The PostgreSQL Company, serving since 1997


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: Jeff Davis
Date:
Subject: Re: NOT NULL with CREATE TYPE
Next
From: Tom Lane
Date:
Subject: Re: why dropping a trigger may cause a deadlock