From: | Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: track ddl changes on single database |
Date: | 2007-06-11 14:36:21 |
Message-ID: | 466D5DE5.5000409@zg.htnet.hr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Rikard Pavelic <rikard(dot)pavelic(at)zg(dot)htnet(dot)hr> 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
>
>
;(
I'm having trouble with this one.
If postgresql.conf has log_statement=none
and I execute log_statement=ddl on mydb
I don't see any ddl in pg_log
So I tried setting log_statement=ddl in postgresql.conf
and I see ddl from all databases in pg_log
I tried "Alter database other_db set log_statement=none"
but it's ddl changes still appears in pg_log
Anyway, it's not a big deal,
I can extract ddl which I need based on log_line_prefix and %d
Regards,
Rikard
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Kovalevski | 2007-06-11 14:37:49 | Re: odbc with encrypted ssl key? |
Previous Message | Pit M. | 2007-06-11 14:03:19 | Re: transaction problem using cursors |