Tom Lane wrote:
> Rikard Pavelic <[EMAIL PROTECTED]> writes:
>
>> I'm looking for recommendation for tracking DDL changes on
>> single database instance.
>>
>
> Perhaps "ALTER DATABASE mydb SET log_statement = ddl" would do what
> you want.
>
> regards, tom lane
>
>
Rikard Pavelic <[EMAIL PROTECTED]> writes:
> I'm looking for recommendation for tracking DDL changes on
> single database instance.
Perhaps "ALTER DATABASE mydb SET log_statement = ddl" would do what
you want.
regards, tom lane
---(end of broadcast
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 <[EMAIL PROTECTED]> wrote:
> >
> >Hi!
> >
> >I'm looki
you can modify log_line_prefix to contain database name.
depesz
On 6/11/07, Rikard Pavelic <[EMAIL PROTECTED]> 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
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 lik
