Re: Determining that a schema has changed for purpose of monitoring

From: Chris <dmagick(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Determining that a schema has changed for purpose of monitoring
Date: 2012-10-04 05:45:38
Message-ID: 506D2282.3090504@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 04/10/12 01:48, Thor Michael Støre wrote:
> Hello.
>
> Is there a way in PostgreSQL for a client to determine that a database schema may have changed since it checked it earlier, for example to get the transaction ID or timestamp of the last successfully committed transaction that included DDL commands and compare them over time? For a while I've also seen plans and bits of work related to DDL triggers that might help me but don't have track of where this stands today.
>
> The background is that I've created a runtime application testing tool and that information would be useful to me, as it's currently manually triggered and I'm looking to explore the possibility of making applications capable of performing non-invasive self-testing with minimal configuration or work needed, at first to the extent of verifying that SQL statements parse and that the types and constraints of their fields don't change in a way that could cause problems for the application.

check_postgres might come in handy for this. See
http://bucardo.org/check_postgres/check_postgres.pl.html#same_schema

--
Postgresql & php tutorials
http://www.designmagick.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Swayam Prakash Vemuri 2012-10-04 06:52:55 Moving from Java 1.5 to Java 1.6
Previous Message Rhys A.D. Stewart 2012-10-04 05:16:12 Re: user defined XML aggregate not working as (i think) it should