| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: table name size |
| Date: | 2016-07-01 14:03:39 |
| Message-ID: | 17906.1467381819@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> writes:
> Is there any specific reason not releasing any version with "NAMEDATALEN 255"
> in file src/include/pg_config_manual.h ?
It would bloat the system catalogs by a rather substantial amount, as well
as in-memory images of those catalogs (catcaches). Seeing that the field
demand for this is next to nil, we're not very likely to do it just for
nominal standards compliance. But you're free to build your own copy that
way if you like --- that's why it's configurable.
BTW, you might as well set it to 256 not 255: alignment considerations
mean that the odd byte would just be wasted in most or all of the
catalogs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shankha | 2016-07-01 14:26:27 | Update multiple rows in a table with different values |
| Previous Message | Sridhar N Bamandlapally | 2016-07-01 10:18:51 | Re: Sub-query having NULL row returning FALSE result |