| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Prepared Statement Name Truncation |
| Date: | 2012-11-23 15:53:48 |
| Message-ID: | 19759.1353686028@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Euler Taveira <euler(at)timbira(dot)com> writes:
> On 22-11-2012 04:27, Pavel Stehule wrote:
>>> significantly larger catalog
> Less than 5% of catalog columns? I don't buy your argument.
It's not about count, it's about size. For instance, pg_attribute
currently requires 140 bytes per row (counting the tuple header and
line pointer), so adding 64 bytes would represent 45% bloat. In
a database with lots of tables that would be painful.
We could avoid this problem if we were prepared to make type "name"
be varlena, but that would be rather catastrophic because of the
code's habit of overlaying C structures onto catalog rows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-11-23 16:10:18 | Re: [GENERAL] Prepared Statement Name Truncation |
| Previous Message | Pavel Stehule | 2012-11-23 11:33:20 | Re: Prepared Statement Name Truncation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-11-23 16:10:18 | Re: [GENERAL] Prepared Statement Name Truncation |
| Previous Message | Adrian Klaver | 2012-11-23 14:53:15 | Re: ERROR: query has no destination for result data |