Re: [GENERAL] Prepared Statement Name Truncation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Euler Taveira <euler(at)timbira(dot)com>, 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 16:34:37
Message-ID: 20522.1353688477@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 23.11.2012 17:53, Tom Lane wrote:
>> We could avoid this problem if we were prepared to make type "name"
>> be varlena, ...

> It would actually be nice to do that because it would *reduce* the
> amount of space and memory used for the catalogs in the typical case,

Agreed, that would be a nicer place to be ... but the amount of work
required to get there is daunting, and rather out of proportion to the
benefit IMO.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-11-23 22:44:21 Re: BUG #7683: pg_upgrade missing configuration file
Previous Message Heikki Linnakangas 2012-11-23 16:10:18 Re: [GENERAL] Prepared Statement Name Truncation

Browse pgsql-general by date

  From Date Subject
Next Message Peter Kroon 2012-11-23 18:13:46 Npgsql
Previous Message Heikki Linnakangas 2012-11-23 16:10:18 Re: [GENERAL] Prepared Statement Name Truncation