Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id EAA13819 for postgres-redist; Mon, 1 May 1995 04:46:03 -0700
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199505011146.EAA13819@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from faui45.informatik.uni-erlangen.de (root@faui45.informatik.uni-erlangen.de [131.188.2.45]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id EAA13809 for <postgres@nobozo.CS.Berkeley.EDU>; Mon, 1 May 1995 04:44:53 -0700
Received: from behaim.faps.uni-erlangen.de by uni-erlangen.de with SMTP;
	id AA09241 (5.65c-6/7.3w-FAU); Fri, 28 Apr 1995 20:35:43 +0200
Received: from sebaldus.faps.uni-erlangen.de by faps.uni-erlangen.de with SMTP;
	id AA24668 (1.38.193.4/7.3s-FAU); Fri, 28 Apr 1995 20:36:44 +0200
From: Thomas Krebs <krebs@faps.uni-erlangen.de>
Message-Id: <9504281836.AA24668@behaim.faps.uni-erlangen.de>
Subject: Re: SQL Interface (and more) 
To: zen@zen.gklw.co.at (V.Grabner)
Date: Fri, 28 Apr 95 20:34:32 METDST
Cc: postgres@postgres.Berkeley.EDU
In-Reply-To: <199504271511.RAA16755@zen.gklw.co.at>; from "V.Grabner" at Apr 27, 95 5:11 pm
Mailer: Elm [revision: 70.85]
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Mon, 01 May 95 04:46:03 -0700
Resent-XMts: smtp

> We would also be very interested in it.
> 
> There are also a few things:
> 
> We are using postgres on 2 different platforms (Linux + SunOs) 
> here for a about a year, have it in CVS an we've it patched a lot.
> 
I have also a number of patches done, I could commit.

> (minor bugs, changes (like "copy to,from"), stability enhancements, etc)
> 
> We also have a list of "don't use" here, like
> 
> hash indices		-> break postgres (reproducable)
> the abstime type 	-> only seem to work without DST
> some array statements	-> make the backend core-dump
> records > 8K data	-> destroy the database with post mortem warning
> etc ..
> 
> and we also extented some #defines like NBACKENDS and stuff for
> large scale databases.
> 
> The question is:
> 
> Are there enough people interrested to do a (public) project kind of like 
> Postgres95, where we could fix some major problems , extend the monster and 
> add the fault tolerance needed for normal use ?
> 
Maybe an group could be built to manage a central source repository, where
hackers could send their patches to, and maybe an active developers group
is growing out of that.
Opinions???

Thomas
--
Thomas Krebs
Department for Manufacturing Automation and Production Systems FAPS
University of Erlangen
Egerlandstr. 7-9
91058 Erlangen
Tel.: +49 (0)9131/85-8740
Fax:  +49 (0)9131/302528
http://www.faps.uni-erlangen.de:1200/persons/krebs.html

==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/
