Re: [HACKERS] Longer Column Names - Mailing list pgsql-hackers

From Jeff MacDonald
Subject Re: [HACKERS] Longer Column Names
Date
Msg-id Pine.BSF.4.10.10002071419070.10395-100000@rage.hub.org
Whole thread Raw
In response to Re: [HACKERS] Longer Column Names  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Longer Column Names
List pgsql-hackers
Ok sounds good then. got a few questions..

1: how to change this (i assume it's in the source, and not a
configure otpion)

2: will it require and initdb , backup, reinstall . or just
recompilie and let her rip.

jeff


======================================================
Jeff MacDonaldjeff@pgsql.com    irc: bignose on EFnet
======================================================

On Mon, 7 Feb 2000, Tom Lane wrote:

> "Jeff MacDonald <jeff@pgsql.com>" <jeffm@pgsql.com> writes:
> > Will Postgres suffer any major performance hits from
> > recomiling with support for column names over 32 chars.
> > ie: 64 chars.
> 
> I doubt it'd make a large difference, except that your system
> tables would get bigger.  Try it and let us know what you see...
> 
>             regards, tom lane
> 
> ************
> 



pgsql-hackers by date:

Previous
From: Alfred Perlstein
Date:
Subject: fsync alternatives (was: Re: [HACKERS] TODO item)
Next
From: Bruce Momjian
Date:
Subject: Re: fsync alternatives (was: Re: [HACKERS] TODO item)