| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ignore_system_indexes affects DROP SCHEMA ... CASCADE reported number of objects dropped |
| Date: | 2018-05-04 04:59:41 |
| Message-ID: | 874ljo81ck.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Peter" == Peter Geoghegan <pg(at)bowt(dot)ie> writes:
Peter> There are a couple of other odd things that look related, such
Peter> as this extract from the triggers.out section of my
Peter> regression.diffs:
That one is pretty obvious (from RelationBuildTriggers):
* Note: since we scan the triggers using TriggerRelidNameIndexId, we will
* be reading the triggers in name order, except possibly during
* emergency-recovery operations (ie, IgnoreSystemIndexes). This in turn
* ensures that triggers will be fired in name order.
Nothing in the code attempts to preserve the order of trigger firing in
the ignore_system_indexes=on case.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksandr Parfenov | 2018-05-04 05:42:44 | Optimze usage of immutable functions as relation |
| Previous Message | Mike Palmiotto | 2018-05-04 04:47:09 | Re: Proper way to reload config files in backend SIGHUP handler |