From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER TABLE ... NOREWRITE option |
Date: | 2012-12-05 17:14:10 |
Message-ID: | m2ip8gmnfh.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 5 December 2012 09:46, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>> On 12/5/2012 1:42 AM, Simon Riggs wrote:
>>>
>>> I think we need a parameter called
>>>
>>> schema_change_reporting = off (default) | on [USERSET]
>>>
>>> which displays relevant statistics/reports about the actions taken by
>>> DDL statements. That will also highlight locks and the need to reduce
>>> their lock levels.
>>
>>
>> where does this get displayed? is it just tossed into the postgres log
>> files?
>
> Good question. Where would you like?
What about pg_stat_ddl, a new system's view? It would maybe need to
have some xid/cid like ordering to be able to reproduce the script. It
could also maybe use the ddl_rewrite module I'm working on for the event
triggers framework, as far as "normalized SQL" goes.
The rewrite information would be a boolean column in that view, I guess.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2012-12-05 17:14:52 | Re: json accessors |
Previous Message | Andres Freund | 2012-12-05 17:14:09 | Re: PITR potentially broken in 9.2 |