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 IAA22551 for postgres-redist; Thu, 27 Apr 1995 08:14:10 -0700 Resent-From: POSTGRES mailing list Resent-Message-Id: <199504271514.IAA22551@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 Relay1.Austria.EU.net (relay1.Austria.EU.net [192.92.138.47]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id IAA22536 for ; Thu, 27 Apr 1995 08:13:48 -0700 Received: from zen.gklw.co.at by Relay1.Austria.EU.net with UUCP id AA15033 (5.67b/IDA-1.5 for postgres@nobozo.CS.Berkeley.EDU); Thu, 27 Apr 1995 17:13:01 +0200 Received: from zen.gklw.co.at (localhost [127.0.0.1]) by zen.gklw.co.at (8.6.11/8.6.11) with SMTP id RAA16755 for ; Thu, 27 Apr 1995 17:11:27 +0200 Message-Id: <199504271511.RAA16755@zen.gklw.co.at> X-Mailer: exmh version 1.6gamma 3/31/95 To: postgres@postgres.Berkeley.EDU Subject: Re: SQL Interface (and more) In-Reply-To: Your message of "Thu, 27 Apr 1995 09:32:57 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Apr 1995 17:11:26 +0200 From: "V.Grabner" Resent-To: postgres-redist@postgres.Berkeley.EDU Resent-Date: Thu, 27 Apr 95 08:14:09 -0700 Resent-XMts: smtp > > Postgres95 has been tested on Alpha (OSF 2.1, 3.0), DECStation (Ultrix 4.4), > > SPARC (SunOS 4.1.3), SPARC (Solaris 2.4), HP 9000/700 (HPUX 9.0). An NT > > port is in the works. 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. (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 ? --zen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Vinzenz Grabner Voice : + 43 1 817 62 30-11 GKL&W GmbH. Fax : + 43 1 817 62 30-17 Schoenbrunnerstr. 179/II/4.St. A-1120 Vienna/Austria/Europe e-mail : zen@gklw.co.at - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ============================================================================== 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/