Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id PAA33254; Tue, 1 Jun 1999 15:18:07 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id PAA04373; Tue, 1 Jun 1999 15:17:49 -0400 (EDT) From: Bruce Momjian Message-Id: <199906011917.PAA04373@candle.pha.pa.us> Subject: Re: [ADMIN] Re: [SQL] Data recovery In-Reply-To: from Jan Wieck at "Jun 1, 1999 09:01:39 pm" To: Jan Wieck Date: Tue, 1 Jun 1999 15:17:49 -0400 (EDT) CC: tgl@sss.pgh.pa.us, bkruger@mindspring.com, pgsql-admin@postgreSQL.org, pgsql-general@postgreSQL.org, pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > Very, very hard, but not impossible. If you update a row, and do a > > select on that row, the select updates the transaction status so the > > next select doesn't need to look at the pg_log table. What this means > > is that pg_log could probably be reconstructed from existing data, with > > just 'unselected' changes not appearing properly. > > So at the end you have some data that you cannot trust. I > don't think that's worth the efford. Yes. True. It is just a point that came up recently when Tom found the first select on a table slow. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026