| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deprecating RULES |
| Date: | 2012-10-22 19:09:43 |
| Message-ID: | 20121022190943.GA5252@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner escribió:
> [I'm replying to Robert's message only because it is the latest on
> the thread; I'm actually kinda replying to the whole thread in
> general.]
Thanks for the great summary.
> (4) Subsequent discussion has produced a few shadowy hints at what
> such uses look like, with the most concrete being a one-time load of
> partitions, for which rules are apparently one or two orders of
> magnitude faster than FOR EACH ROW truggers. There was also a mention
> of writing to a log table being easier. Out of 100+ messages on this
> thread, I can't recall anything else that wasn't pretty vague.
I think enabling OLD/NEW in FOR EACH STATEMENT triggers would go a long
way.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2012-10-22 19:47:37 | Re: [PATCH] Prefetch index pages for B-Tree index scans |
| Previous Message | Tom Lane | 2012-10-22 18:34:29 | Re: ToDo: KNN Search should to support DISTINCT clasuse? |