| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sql_drop Event Triggerg |
| Date: | 2013-03-26 19:49:59 |
| Message-ID: | 20130326194959.GD3881@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas escribió:
> On Tue, Mar 26, 2013 at 3:02 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > Now there *is* one rather big performance problem in this patch, which
> > is that it turns on collection of object dropped data regardless of
> > there being event triggers that use the info at all. That's a serious
> > drawback and we're going to get complaints about it. So we need to do
> > something to fix that.
>
> Really? Who is going to care about that? Surely that overhead is
> quite trivial.
I don't think it is, because it involves syscache lookups for each
object being dropped, many extra pallocs, etc. Surely that's many times
bigger than the PG_TRY overhead you were worried about.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2013-03-26 19:59:23 | Re: spoonbill vs. -HEAD |
| Previous Message | viod | 2013-03-26 19:48:41 | GSoC project : K-medoids clustering in Madlib |