Re: track ddl changes on single database - Mailing list pgsql-general

From Ray Stell
Subject Re: track ddl changes on single database
Date
Msg-id 20070611124302.GB714@cns.vt.edu
Whole thread Raw
In response to Re: track ddl changes on single database  ("hubert depesz lubaczewski" <depesz@gmail.com>)
List pgsql-general
On Mon, Jun 11, 2007 at 12:55:08PM +0200, hubert depesz lubaczewski wrote:
> you can modify log_line_prefix to contain database name.

%d = database name
restart required

a trigger might be cleaner.




> depesz
>
> On 6/11/07, Rikard Pavelic <rikard.pavelic@zg.htnet.hr> wrote:
> >
> >Hi!
> >
> >I'm looking for recommendation for tracking DDL changes on
> >single database instance.
> >
> >Currently I'm using pg_log to extract DDL changes, but those changes
> >are cluster wide.
> >
> >Ideally I would like to enable option in pg_log to give me info about
> >in which database changes were made.
> >Something like
> >timestamp DB: my_database LOG: statement: "DDL statement here..."
> >
> >Is there such an option, or any other suggestion how to track
> >these changes?
> >
> >Thanks,
> >Rikard
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 9: In versions below 8.0, the planner will ignore your desire to
> >       choose an index scan if your joining column's datatypes do not
> >       match
> >
>
>
>
> --
> http://www.depesz.com/ - nowy, lepszy depesz

pgsql-general by date:

Previous
From: "Mike Gould"
Date:
Subject: Distributing PostGres database to various customers
Next
From: Thomas Pundt
Date:
Subject: Re: transaction problem using cursors