Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] char types gone.

From: wward <wward(at)gwi(dot)net>
To: Darren King <darrenk(at)insightdist(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] char types gone.
Date: 1998-03-24 11:01:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I think Darren brings up very good points here. This seems to be the model
that many people are going to when developing large systems. This would
also help in maintaning the the system.

On Mon, 23 Mar 1998, Darren King wrote:

> > fact, I want to bring in the IP code from contrib as part of
> > the core yet...
> Would be nice if stuff like that (and the money and geometrics) could be
> compiled in in the same manner that Apache is a basic web server that lets
> you pick and choose modules/features you want to build into it.
> I don't know how big of a performance boost it provides in the cache, but
> removing the functions associated with the char types shrank the pg_proc
> table from 906 to 842 entries or a bit over 7%.
> Want to shrink it further?  Of those remaining 842, _230_ are for the geometric
> types!  Throw in 25 more for the cash/money functions.  Bloat city if you
> never use these things.  Thirty percent could be moved out to contrib and
> not missed by most postgres users.
> I think a reasonable goal is to provide an sql server that meets the current sql
> standard with the possibility of having other types and functionality available
> as modules.  These modules could be made into the template1 at compile time
> or made and installed on a per-database basis.  Make your server and database
> with whatever you want in it.
> Why force others to have functionality 'x', 'y' and 'z' when they only want 'y'?
> darrenk

In response to

pgsql-hackers by date

Next:From: Jose' Soares Da SilvaDate: 1998-03-24 11:11:48
Subject: Re: AW: [HACKERS] Re: PostgreSQL reference manual
Previous:From: Michael MeskesDate: 1998-03-24 08:44:36
Subject: Re: AW: [HACKERS] Re: PostgreSQL reference manual

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group