Return-Path: owner-postman Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.37.53]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with ESMTP id SAA07536 for ; Wed, 10 Jan 1996 18:34:16 -0800 Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id SAA04552 for postgres-arch; Wed, 10 Jan 1996 18:34:16 -0800 Message-Id: <199601110234.SAA04552@faerie.CS.Berkeley.EDU> X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol From: aoki@CS.Berkeley.EDU (Paul M. Aoki) To: postgres-arch@postgres.Berkeley.EDU Reply-To: aoki@CS.Berkeley.EDU (Paul M. Aoki) Subject: [aseplim@ntu.ac.sg: ?] Date: Wed, 10 Jan 96 18:34:15 -0800 Sender: aoki@postgres.Berkeley.EDU X-Mts: smtp ------- Forwarded Message From: Lim Ee Peng Date: Tue, 13 Jun 1995 17:28:17 +0800 Dear Paul, I have been running postgres 4.2 on SunOS 4.1 (sparc 20) for the last few months and it was OK. However lately, I encountered problems with pg_time when I queried a table. A script is given below to illustrate the problem. The problem persists even when I tried to restart postmaster. ================================================================================ sentosa% monitor DB_A Welcome to the POSTGRES terminal monitor Go * retrieve (RES_A.all)\g Query sent to backend is "retrieve (RES_A.all)" -------------------------------------------------------------------------------- | RNAME | STREET | BLDGNO | PHONE | FOUNDER | RATING | -------------------------------------------------------------------------------- | r1 | wash ave | -------------------------------------------------------------------------------- | r2 | univ ave | -------------------------------------------------------------------------------- | r3 | snelling ave | -------------------------------------------------------------------------------- | r4 | grand ave | -------------------------------------------------------------------------------- WARN:Jun 13 16:57:26:cannot open segment 1 of relation pg_time Go * retrieve (RES_A.all)\g Query sent to backend is "retrieve (RES_A.all)" NOTICE:Jun 13 16:57:26:AbortTransaction and not in in-progress state Go * retrieve (RES_A.all)\g Query sent to backend is "retrieve (RES_A.all)" ----------------------------------------------------------------------------------------- | RNAME | STREET | BLDGNO | PHONE | FOUNDER | RATING | CO| ----------------------------------------------------------------------------------------- ====================================================================================== I also note that pg_log is incredibly large. Is it normal? Can we reduce it? -rw------- 1 postgres staff 8192 Jun 7 11:56 pg_database -rw------- 1 postgres staff 0 Apr 21 1994 pg_defaults -rw------- 1 postgres staff 0 Apr 21 1994 pg_demon -rw------- 1 postgres staff 0 Apr 21 1994 pg_group -rw------- 1 postgres staff 134234112 Jun 13 16:58 pg_log -rw------- 1 postgres staff 0 Apr 21 1994 pg_magic -rw------- 1 postgres staff 0 Apr 21 1994 pg_server -rw------- 1 postgres staff 81920 Jun 13 12:42 pg_time -rw------- 1 postgres staff 8192 May 22 19:16 pg_user -rw------- 1 postgres staff 8192 Jun 13 16:57 pg_variable Thanks, Ee-Peng Lim Sch of Applied Science Nanyang Tech Univ. ------- End of Forwarded Message -- Paul M. Aoki | University of California at Berkeley aoki@CS.Berkeley.EDU | Dept. of EECS, Computer Science Division (#1776) | Berkeley, CA 94720-1776