RE: Some advanced database features, are they present in PostgreSQL

I have to tell you guys that his is the major limiting factor that has
kept us away from PGSQL for major projects. This looks great. Now, two
questions.

How much of what is on the page is what it will eventually do and how much
will there actually be in the beta.

Also, the site talks about data hierarchy replication. Is this similar to
segmentation where each site sees the information that is of interest to
them but not the info from all other sites? We have kind of the hub and
spoke situation where the corporate office gets everything from all the
sites, but the sites only get info from the home office that is of interest
to them. We were going to do this by segmenting the database into site
specific segments and only replicating that segment to the appropriate
site...

Thanks,
Rob

-----Original Message-----
From: pgsql-general-owner(at)hub(dot)org [mailto:pgsql-general-owner(at)hub(dot)org]On
Behalf Of The Hermit Hacker
Sent: Tuesday, October 10, 2000 8:34 PM
To: Rob Hutton
Cc: 'Peter Eisentraut'; 'Marc SCHAEFER'; pgsql-general(at)postgresql(dot)org
Subject: RE: [GENERAL] Some advanced database features, are they present
in PostgreSQL

right now, we are working with our partners internally on this, before we
release it publicly, but more information can be found at:

http://www.erserver.com/

On Tue, 10 Oct 2000, Rob Hutton wrote:

> I'm looking for info about the synching and I don't see any. Is there a
> more specific URL and is there a time frame for this. Also, has
> segmentation been discussed?
>
> -----Original Message-----
> From: pgsql-general-owner(at)hub(dot)org [mailto:pgsql-general-owner(at)hub(dot)org]On
> Behalf Of Peter Eisentraut
> Sent: Tuesday, October 10, 2000 1:08 PM
> To: Marc SCHAEFER
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Some advanced database features, are they present
> in PostgreSQL
>
>
> Marc SCHAEFER writes:
>
> > - log all transactions to a special log file, that can be used for
> > backup purposes:
>
> Will be in 7.1.
>
> > - hard transactions: cutting the power to a PostgreSQL server
> > may cause data loss and/or data corruption. Some databases use
> > sophisticated techniques to ensure serialization of operation
> > through journaling, redoing some of the transactions at
> > bootup time if required.
>
> This is really the same as above in implementation. So same answer.
>
> > - the ability to synchronize two database servers, with only the
> > changes being exchanged, live. Or the ability to have many
> > servers in a load-balancing or data scattering pool.
>
> Something like this has recently been announced as add-on from PostgreSQL,
> Inc. (www.pgsql.com) Haven't seen it used, though.
>
> > - ability to have databases bigger than the host's maximum file size
>
> That has been available for quite a while.
>
> --
> Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
>
>
>

Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary:
scrappy(at){freebsd|postgresql}.org