agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedFrom: Paul M. Aoki <aoki@CS.Berkeley.EDU>
To: postgres-arch@postgres.Berkeley.EDU
Subject: [aseplim@ntu.ac.sg: ?]
Date: Wed, 10 Jan 96 18:34:15 -0800
Message-ID: <199601110234.SAA04552@faerie.CS.Berkeley.EDU> (raw)
------- Forwarded Message
From: Lim Ee Peng <aseplim@ntu.ac.sg>
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|
-----------------------------------------------------------------------------------------
<tuples>
<monitor hangs here !>
======================================================================================
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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: postgres@postgres.berkeley.edu
Cc: aoki@CS.Berkeley.EDU, postgres-arch@postgres.Berkeley.EDU
Subject: Re: [aseplim@ntu.ac.sg: ?]
In-Reply-To: <199601110234.SAA04552@faerie.CS.Berkeley.EDU>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox