| From: | "Jeff MacDonald <jeff(at)pgsql(dot)com>" <jeffm(at)pgsql(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff MacDonald <jeff(at)pgsql(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Longer Column Names |
| Date: | 2000-02-07 18:20:06 |
| Message-ID: | Pine.BSF.4.10.10002071419070.10395-100000@rage.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 MacDonald
jeff(at)pgsql(dot)com irc: bignose on EFnet
======================================================
On Mon, 7 Feb 2000, Tom Lane wrote:
> "Jeff MacDonald <jeff(at)pgsql(dot)com>" <jeffm(at)pgsql(dot)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
>
> ************
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-02-07 18:27:20 | Re: fsync alternatives (was: Re: [HACKERS] TODO item) |
| Previous Message | Bruce Momjian | 2000-02-07 17:36:29 | Re: [HACKERS] New Globe |