Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4F6F59FB205 for ; Wed, 29 Nov 2006 11:50:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 79789-02 for ; Wed, 29 Nov 2006 11:50:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 16DFD9FB1E6 for ; Wed, 29 Nov 2006 11:50:46 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kATFojtD019765; Wed, 29 Nov 2006 10:50:45 -0500 (EST) To: Alessandro Baretta cc: pgsql-performance@postgresql.org Subject: Re: NAMEDATALEN and performance In-reply-to: <456D6FAB.4030400@studio.baretta.com> References: <456D6FAB.4030400@studio.baretta.com> Comments: In-reply-to Alessandro Baretta message dated "Wed, 29 Nov 2006 12:31:55 +0100" Date: Wed, 29 Nov 2006 10:50:45 -0500 Message-ID: <19764.1164815445@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/266 X-Sequence-Number: 22036 Alessandro Baretta writes: > I am considering the possibility of rebuilding the server with > NAMEDATALEN equal to 256. I have seen an interesting thread [1] about > the performance impact of raising NAMEDATALEN, but it did not seem > conclusive. More to the point, tests done on 7.2-era code shouldn't be assumed to be relevant to modern PG releases. I think you'll need to do your own benchmarking if you want to find out the costs of doing this. regards, tom lane