From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | V S P <toreason(at)fastmail(dot)fm>, postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [Q] sequence and index name limits in 8.4 |
Date: | 2009-06-28 02:19:15 |
Message-ID: | 24275.1246155555@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Sat, Jun 27, 2009 at 7:09 PM, V S P<toreason(at)fastmail(dot)fm> wrote:
>> Searched docs and the web but only saw references to the older version
>> of postgres
>> where changing source code was recommended ( NAMEDATALEN) if more than
>> 31 characters
>> in the names are desired.
> Unless you want to compile your own version, I think the curent limit
> is 64 or 63 characters. There are real and measurable performance hits
> as you go over that number.
Also, it hasn't been 32 by default since 7.2, more than seven years ago.
Whatever references you are reading are so out of date as to be
completely untrustworthy ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-06-28 03:02:51 | Re: Switching from MySQL: ON DUPLICATE KEY UPDATE, plpgsql function |
Previous Message | Scott Marlowe | 2009-06-28 01:47:11 | Re: [Q] sequence and index name limits in 8.4 |