From: | Alessandro Baretta <a(dot)baretta(at)studio(dot)baretta(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | NAMEDATALEN and performance |
Date: | 2006-11-29 11:31:55 |
Message-ID: | 456D6FAB.4030400@studio.baretta.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Gentlemen,
I use a modeling language which compiles down to a fairly verbose SQL DDL. If I
use semantically transparent identifiers in the modeling language, the compiler
easily generates identifiers much longer than the default value of NAMEDATALEN.
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. Are there commonly accepted
correlations between NAMEDATALEN and server performance? How would raising its
value impact disk usage?
[1] http://archives.postgresql.org/pgsql-hackers/2002-04/msg01253.php
--
*********************************************************************
Ing. Alessandro Baretta
Studio Baretta
http://studio.baretta.com/
Consulenza Tecnologica e Ingegneria Industriale
Technological Consulting and Industrial Engineering
Headquarters
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Lab
tel. +39 02 9880 271
fax. +39 02 9828 0296
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Hurt | 2006-11-29 13:25:57 | Re: RES: Priority to a mission critical transaction |
Previous Message | Ron Mayer | 2006-11-29 10:55:48 | Re: RES: Priority to a mission critical transaction |