| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Prepared Statement Name Truncation |
| Date: | 2012-11-23 11:33:20 |
| Message-ID: | CAFj8pRBk5W-4twexSK3n0f_3msrAVDALGJOyi6=iGJcB+pxeFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
2012/11/23 Euler Taveira <euler(at)timbira(dot)com>:
> On 22-11-2012 04:27, Pavel Stehule wrote:
>> 2012/11/21 Greg Sabino Mullane <greg(at)turnstep(dot)com>: Separately, what are
>> the objections to raising the size limit to 128?
>>
>>> significantly larger catalog
>>
> Less than 5% of catalog columns? I don't buy your argument.
default 6201kB (64) updated 6967kB (128) on empty database - so it is
12% more per one database
in our warehouses we have more than 100000 relations per database and
about 1000 databases per warehouse - so these number can be
significantly higher
second issue can be increasing memory allocations for system caches
and some other place
Regards
Pavel
>
>
> --
> Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
> PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-23 15:53:48 | Re: [GENERAL] Prepared Statement Name Truncation |
| Previous Message | Euler Taveira | 2012-11-23 11:00:28 | Re: Prepared Statement Name Truncation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-11-23 14:53:15 | Re: ERROR: query has no destination for result data |
| Previous Message | Peter Kroon | 2012-11-23 11:25:42 | Re: ERROR: query has no destination for result data |