Return-Path: pg_adm@postgres.berkeley.edu Received: by postgres.Berkeley.EDU (5.61/1.29) id AA09932; Tue, 18 Aug 92 09:57:51 -0700 Date: Tue, 18 Aug 92 09:57:51 -0700 Message-Id: <9208181657.AA09932@postgres.Berkeley.EDU> From: Sean Levy Subject: Bizarre problems with V3R1 on DS5000/200 (Ultrix 4.2) To: postgres@postgres.berkeley.edu Sender: pg_adm@postgres.berkeley.edu For various reasons, I am running 3.1 on a DS5000/200 (I'm waiting for 4.0.1). Until today, my application worked wonderfully, both locally and across the net. Today, I started getting the following, inexplicable, bizarre behavior: * I get NOTICE messages about the hash memory being too small and having to be expanded * I get "Fixing up unaligned memory access" messages from the backend constantly * My queries don't return; I just get those unaligned access messages pumped out ad inf. until I kill off the postmaster and backend * Ultrix complains about the error logger not being able to store error messages, also interminably, until I kill the postmaster and/or backend In short, everything is screwed, nothing works, and I haven't changed a thing. This happens whether or not I'm running on the same machine as the backend runs on, with or without PGHOST set and from a remote machine, all via libpq. My one hypothesis is: I just wrote a script for a user to run my application and load in around 6000 objects, which would result in 6000 instances each being created in two classes in the RDBMS. My suspicion is that somehow this massive creation of objects has fucked things up in postgres somehow, but I don't know how. Anyone who can shed some light on this, please do. I can recreate the situation and post exact messages, but was hoping that this was familiar to someone out there... Cheers, -- Sean -- Sean Levy, n-dim Group, EDRC, CMU, 5000 Forbes Ave, PGH, PA 15213 Email: snl+@cmu.edu, Phone: +1 412 268 5221, Fax: +1 412 268 5229