Return-Path: postman 
Delivery-Date: Thu, 14 Oct 93 14:55:21 PDT
Return-Path: postman
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA12529; Thu, 14 Oct 93 14:45:50 -0700
Resent-From: postman (POSTGRES mailing list)
Resent-Message-Id: <9310142145.AA12529@postgres.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: witr@rwwa.COM
Received: from relay1.UU.NET by postgres.Berkeley.EDU (5.61/1.29)
	id AA12521; Thu, 14 Oct 93 14:45:36 -0700
Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP 
	(5.61/UUNET-internet-primary) id AB20678; Thu, 14 Oct 93 17:49:03 -0400
Date: Thu, 14 Oct 93 17:49:03 -0400
From: witr@rwwa.COM
Message-Id: <9310142149.AB20678@relay1.UU.NET>
Received: from spooky.UUCP by uucp2.uu.net with UUCP/RMAIL
	(queueing-rmail) id 174742.22478; Thu, 14 Oct 1993 17:47:42 EDT
To: postgres@postgres.berkeley.edu
Subject: Does purging work in 4.1
Content-Type: text
Content-Length: 751
Resent-To: postgres-dist
Resent-Date: Thu, 14 Oct 93 14:45:48 PDT

Does PURGEing work in Postgres 4.1?

If I create a db and a relation *WITHOUT* vacuuming and do a purge,
the purge command succeeds but the backend can no longer find the
relation.

If I create a db and a relation *WITH* vacuuming and do a purge,
the purge command fails.

vacuum.c seems to be setting the pg_class.relpreserved field to an
abstime whereas the rest of the code is expecting this to be a
relative time, which would explain the latter behavior, but I don't
know what is causing the former behavior.

P.S., if I vacuum the db *after* the successfull purge, the backend
coredumps. 

---
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
