From: | "Petr Jelinek" <pjmodos(at)pjmodos(dot)net> |
---|---|
To: | "'Josh Berkus'" <josh(at)agliodbs(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE ... NOREWRITE option |
Date: | 2012-12-05 13:24:46 |
Message-ID: | 000001cdd2eb$f0822160$d1866420$@pjmodos.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-
> owner(at)postgresql(dot)org] On Behalf Of Josh Berkus
> Sent: 05 December 2012 01:17
> To: Tom Lane
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] ALTER TABLE ... NOREWRITE option
>
> However, as I said, if we had the EXPLAIN ALTER, we could use auto-explain
> to log the ALTER plans (finally, a good use for auto-explain). So that's a
> workable workaround. And EXPLAIN ALTER would offer us more flexibility
> than any logging option, of course.
>
+1
And for the minority who wants to check themselves (like me) in their tooling this is also usable solution.
Regards
Petr Jelinek
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-12-05 13:34:05 | Re: PITR potentially broken in 9.2 |
Previous Message | Amit Kapila | 2012-12-05 12:32:01 | Re: Switching timeline over streaming replication |