| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER TABLE ... NOREWRITE option |
| Date: | 2012-12-05 22:41:21 |
| Message-ID: | CA+U5nMJ7JMp3cVj=sYAqEEsVF4ofjd9rGUAaVauz2Fwf+fMKWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 December 2012 22:21, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>>> CREATE EVENT TRIGGER my_event_trigger
>>> ON table_rewrite
>>> EXECUTE PROCEDURE consider_whether_to_throw_an_error();
>>
>> +1, I was just thinking that myself.
>
> +1, and I think that can happen for 9.3, as soon as we agree on the list
> of code points where we want that event to fire. ALTER TABLE variants
> that are rewriting the heap, sure. CLUSTER? VACUUM FULL? TRUNCATE?
Events needed
* Table rewrite
* Index rebuild
* Relation scan (index/table/toast etc)
* AccessExclusiveLock
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2012-12-05 22:43:05 | Re: Dumping an Extension's Script |
| Previous Message | Andres Freund | 2012-12-05 22:31:20 | Re: Dumping an Extension's Script |