Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: NAMEDATALEN and performance
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Alessandro Baretta <a(dot)baretta(at)studio(dot)baretta(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: NAMEDATALEN and performance
- Date: Wed, 29 Nov 2006 10:50:45 -0500
Alessandro Baretta <a(dot)baretta(at)studio(dot)baretta(dot)com> 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
- References:
- NAMEDATALEN and performance
- From: Alessandro Baretta
- NAMEDATALEN and performance
- Prev by Date: Re: RES: Priority to a mission critical transaction
- Next by Date: Re: RES: Priority to a mission critical transaction
- Previous by thread: NAMEDATALEN and performance
- Next by thread: OT - how to size/match multiple databases/apps for a single server
- Indexes: