X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D6EAE5E46C3 for ; Wed, 18 Aug 2004 18:39:20 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 65455-07 for ; Wed, 18 Aug 2004 21:39:22 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 667F35E3F15 for ; Wed, 18 Aug 2004 18:39:12 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7ILdLRO004153; Wed, 18 Aug 2004 17:39:21 -0400 (EDT) To: apb18@cornell.edu Cc: pgsql-performance@postgresql.org Subject: Re: Array types and loading In-reply-to: <19ab0ccd040818123936c1cdd3@mail.gmail.com> References: <19ab0ccd040818123936c1cdd3@mail.gmail.com> Comments: In-reply-to Aaron Birkland message dated "Wed, 18 Aug 2004 15:39:29 -0400" Date: Wed, 18 Aug 2004 17:39:21 -0400 Message-ID: <4152.1092865161@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/280 X-Sequence-Number: 7916 Aaron Birkland writes: > In a nutshell, it looks like whenever COPY is invoked, and when a user > defined type is used in an array, then stat64() will be called for > each row accessed on the shared library relevant for the user defined > type. Let me guess ... PG 7.3 or older? 7.4 should avoid the problem because array_in() caches function lookup information for the element type's input function across multiple calls. In 8.0 there's also a cache at the fmgr_info() level to eliminate repeated searches for a dynamically loaded function. regards, tom lane