Re: Big 7.1 open items

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)yahoo(dot)com>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Big 7.1 open items
Date: 2000-06-15 02:46:39
Message-ID: 3.0.1.32.20000614194639.011b5c50@mail.pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

At 10:28 PM 6/14/00 -0400, Bruce Momjian wrote:

>As far as pg_log, you certainly would not expect to get any information
>back from the time of the backup table to current, so the current pg_log
>would be just fine.

In reality, very few people are going to be interested in restoring
a table in a way that breaks referential integrity and other
normal assumptions about what exists in the database. The reality
is that most people are going to engage in a little time travel
to a past, consistent backup rather than do as you suggest.

This is going to be more and more true as Postgres gains more and
more acceptance in (no offense intended) the real world.

>Right now, we use 'ps' with args to display backend information, and ls
>-l to show disk information. We are going to lose that here.

Dependence on "ls -l" is, IMO, a very weak argument.

- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-06-15 02:59:20 input/output functions have been changed ?
Previous Message Bruce Momjian 2000-06-15 02:44:16 Re: Big 7.1 open items

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2000-06-15 03:13:52 Re: Big 7.1 open items
Previous Message Bruce Momjian 2000-06-15 02:44:16 Re: Big 7.1 open items