Re: ALTER TABLE ... NOREWRITE option - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: ALTER TABLE ... NOREWRITE option
Date
Msg-id CA+U5nMK5yGOKFhYub3CuDxXtoRXUy+E5MtNkKuD6whu75WG4Yw@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE ... NOREWRITE option  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER TABLE ... NOREWRITE option  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5 December 2012 15:01, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> John R Pierce <pierce@hogranch.com> writes:
>> 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?
>
> And perhaps more to the point, what's the advantage compared to
> good old "log_statement = ddl"?

That logs DDL statements for the whole system and isn't user settable.
It wouldn't be useful to extend that, since the user wouldn't be able
to enable/disable and the stats would get dumped in the server log.

Need something more user specific.

Ideas

* pg_stat_ddl (from Dimitri) which would be a temp table containing results
* Stream of NOTICE statements back to client.... that seems easier
* err...

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Dumping an Extension's Script
Next
From: Andres Freund
Date:
Subject: Re: Dumping an Extension's Script