Re: PITR Dead horse?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: ntufar(at)pisem(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PITR Dead horse?
Date: 2004-02-05 14:34:44
Message-ID: 200402051434.i15EYiQ23309@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Page wrote:
>
>
> > -----Original Message-----
> > From: Nicolai Tufar [mailto:ntufar(at)pisem(dot)net]
> > Sent: 05 February 2004 00:01
> > To: pgsql-hackers(at)postgresql(dot)org
> > Subject: Re: [HACKERS] PITR Dead horse?
> >
> > Totally agree. Robustness and rock-solidness are the only
> > things missing for PostgreSQL to become the killer of certain
> > commercial enterprise databases out there.
>
> Well I've only been using PostgreSQL since 1997 and the *only* release I
> ever had problems with was 6.3.2. We also use(d) Informix SE, DB2,
> Unidata and SQL Server and only Informix and Unidata come close to the
> robustness of PostgreSQL - and they're not the ones we need to worry
> about.
>
> Now I'm not saying we shouldn't be continually looking to improve
> things, but I don't think this is quite the problem you imply.

I assume he was talking about the lack of data recovery in cases of hard
drive failure --- we now require you restore from backup or use a
replicated machine/drive setup.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Gibson 2004-02-05 14:46:57 dblink - custom datatypes don't work
Previous Message Andrew Dunstan 2004-02-05 14:34:33 Re: [PATCHES] log session end - again