Received: from smtp-1.attica.net.nz (pop3-1.attica.net.nz [202.180.66.199]) by postgresql.org (Postfix) with SMTP id 04C65475461 for ; Fri, 22 Feb 2002 18:47:43 -0500 (EST) Received: (qmail 50918 invoked from network); 22 Feb 2002 23:47:43 -0000 Received: from 202-180-68-221.nas1.wlg.attica.net.nz (202.180.68.221) by pop3-1.attica.net.nz with SMTP; 22 Feb 2002 23:47:43 -0000 Subject: Re: comparision chart From: Mark kirkwood To: clayton cottingham , Josh Berkus Cc: p-sql Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.13 (Preview Release) Date: 23 Feb 2002 12:47:39 +1300 Message-Id: <1014421661.1538.23.camel@spikey.slithery.org> Mime-Version: 1.0 X-Archive-Number: 200202/330 X-Sequence-Number: 6752 Previously... > > Regarding your rating of Postgres, what do you mean by "partial" > support of constraints? And what is "hotBack"? > The confusing terms probably my fault - (Someone probably saw an old posting of mine) - apologies in the time travelled sense... I think partial constraint meant that there was "create" but no "alter/drop/disable/enable" for them (This was circa Pg 7.0.0). And I seem to recall thinking about a hotbackup in the sense of : i) able to back up the db while it is running (and) ii) able to use use the transaction logs to "catch up" after a media failure (assuming the logs are backed up somehow too) Clearly most of the crowd can do i), but fewer do ii) - mainly the commercial ones. I am less sure these days the ii) is so important. Many folks seem to manage by means of using i) combined with replication or fault tolerance at the os or hardware level (but I am ranging off the topic here...) best wishes for the chart regards Mark