From: Manfred Koizar <mkoi-pg@aon.at>
To: shridhar_daithankar@persistent.co.in
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: contrib/fixchar (Was: Large databases, performance)
Date: Thu, 10 Oct 2002 15:30:31 +0200
Message-ID: <aeuaqu8uk5qi6ledajbu8a0kqk2m2c6m3u@4ax.com> (raw)
In-Reply-To: <a2n7qu0qen2ne1chalomdgt5n1etgb4uk3@4ax.com>
References: <3D9C3E05.7070906@clearmetrix.com>
<3DA1A331.21316.F7E742B@localhost>
<a2n7qu0qen2ne1chalomdgt5n1etgb4uk3@4ax.com>
On Wed, 09 Oct 2002 10:00:03 +0200, I wrote:
>here is an implementation of a set of user types: char3, char4,
>char10.
New version available. As I don't want to spam the list with various
versions until I get it right eventually, you can get it from
http://members.aon.at/pivot/pg/fixchar20021010.tgz if you are
interested.
What's new:
. README updated (per Shridhar's suggestion)
. doesn't crash on NULL (p. Tom)
. version-1 calling conventions (p. Tom)
. isCachable (p. Tom)
. works for 7.2 (as delivered) and for 7.3 (make for73)
Shridhar, you were concerned about signed/unsigned chars; looking at
the code I can not see how this is a problem. So no change in this
regard.
Thanks for your comments. Have fun!
Servus
Manfred
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: mkoi-pg@aon.at, shridhar_daithankar@persistent.co.in, pgsql-hackers@postgresql.org, pgsql-performance@postgresql.org
Subject: Re: contrib/fixchar (Was: Large databases, performance)
In-Reply-To: <aeuaqu8uk5qi6ledajbu8a0kqk2m2c6m3u@4ax.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox