From: | "hubert depesz lubaczewski" <depesz(at)gmail(dot)com> |
---|---|
To: | "Rikard Pavelic" <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: track ddl changes on single database |
Date: | 2007-06-11 10:55:08 |
Message-ID: | 9e4684ce0706110355q3df95c3ej5929cff981be9c0e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
you can modify log_line_prefix to contain database name.
depesz
On 6/11/07, Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Nix | 2007-06-11 11:34:48 | Functions that return both Output Parameters and recordsets |
Previous Message | Alban Hertroys | 2007-06-11 10:26:55 | Re: performance problem with loading data |