"Heinemann, Manfred (IMS)" <HeinemannM@xxxxxxxxxx> writes: > I have played around with the postgres memory settings and setting search_path on a function causes a lot more memory to be used than if no search_path was set. That's a pretty broad claim with a pretty small amount of evidence offered. I can certainly believe that attaching a SET clause (whether for search_path or any other GUC variable) would have an efficiency impact; one non-obvious example is that it prevents inlining if the function is a SQL function. But I don't immediately see a reason for major memory consumption from that. I suspect what you're seeing is specific to a particular use-case. If you were to provide a concrete example, we could look into what's happening. regards, tom lane
