Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> writes:
> Pull up isReset flag from AllocSetContext to MemoryContext struct. This
> avoids the overhead of one function call when calling MemoryContextReset(),
> and it seems like the isReset optimization would be applicable to any new
> memory context we might invent in the future anyway.

> This buys back the overhead I just added in previous patch to always call
> MemoryContextReset() in ExecScan, even when there's no quals or projections.

Do you actually have any measurements that prove that?  This seems like
a rather ugly destruction of a modularity boundary in return for a
hypothetical performance gain.  I'm also concerned that you've probably
added cycles on net to MemoryContextAlloc (where it's no longer possible
to tail-call AllocSetAlloc), which could very easily cost more cycles on
most workloads than could ever be saved by making MemoryContextReset a
shade faster.

			regards, tom lane

In response to

• pgsql: Pull up isReset flag from AllocSetContext to MemoryContextstruc at 2011-05-21 18:54:52 from Heikki Linnakangas

Responses

• Re: pgsql: Pull up isReset flag from AllocSetContext to MemoryContext struc at 2011-05-23 12:01:54 from Heikki Linnakangas

pgsql-committers by date

Next:	From: Tom Lane	Date: 2011-05-22 19:17:15
	Subject: pgsql: Make plpgsql provide the typmods for its variables to the mainp
Previous:	From: Peter Eisentraut	Date: 2011-05-22 17:07:43
	Subject: pgsql: Clarify the documentation of the --with-ossp-uuid option