From: "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
To: Manfred Koizar <mkoi-pg@aon.at>, pgsql-hackers@postgresql.org,
	pgsql-general <pgsql-general@postgresql.org>,
	pgsql-performance@postgresql.org
Date: Wed, 09 Oct 2002 13:37:13 +0530
MIME-Version: 1.0
Subject: Re: Large databases, performance
Reply-To: shridhar_daithankar@persistent.co.in
Message-ID: <3DA43109.23106.1978CDFD@localhost>
In-reply-to: <a2n7qu0qen2ne1chalomdgt5n1etgb4uk3@4ax.com>
References: <3DA1A331.21316.F7E742B@localhost>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 9 Oct 2002 at 10:00, Manfred Koizar wrote:

> On Mon, 07 Oct 2002 15:07:29 +0530, "Shridhar Daithankar"
> <shridhar_daithankar@persistent.co.in> wrote:
> >Only worry is database size. Postgresql is 111GB v/s 87 GB for mysql.
> 
> Shridhar,
> 
> here is an implementation of a set of user types: char3, char4,
> char10.  Put the attached files into a new directory contrib/fixchar,
> make, make install, and run fixchar.sql through psql.  Then create
> your table as
> 	CREATE TABLE tbl (
> 	type		int,
> 	esn		char10,
> 	min		char10,
> 	datetime	timestamp,
> 	opc0		char3,
> 	...
> 	rest		char4,
> 	field0		int,
> 	field1		char4,
> 	...
> 	)
> 
> This should save 76 bytes per heap tuple and 12 bytes per index tuple,
> giving a database size of ~ 76 GB.  I'd be very interested how this
> affects performance.
> 
> Code has been tested for v7.2, it crashes on v7.3 beta 1.  If this is
> a problem, let me know.

Thank you very much for this. I would certainly give it a try. Please be 
patient as next test is scheuled on monday.

Bye
 Shridhar

--
love, n.:	When it's growing, you don't mind watering it with a few tears.