| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER TABLE ... NOREWRITE option |
| Date: | 2012-12-05 18:11:51 |
| Message-ID: | 9165.1354731111@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 5 December 2012 15:01, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
Not true; you can set it with ALTER ROLE/DATABASE, and a superuser can
adjust it for his own session.
> * pg_stat_ddl (from Dimitri) which would be a temp table containing results
> * Stream of NOTICE statements back to client.... that seems easier
> * err...
And an ORM is going to do what with either, pray tell? None of these
are of any use except with an interactive session; in which the user
could perfectly well use EXPLAIN, anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-05 18:13:19 | Re: Dumping an Extension's Script |
| Previous Message | Tom Lane | 2012-12-05 18:07:35 | Re: Dumping an Extension's Script |