Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA18192; Sat, 8 May 93 14:29:18 -0700
Date: Sat, 8 May 93 14:29:18 -0700
Message-Id: <9305082129.AA18192@postgres.Berkeley.EDU>
From: gerben@rna.indiv.nluug.nl (Gerben Wierda)
Subject: Postgres 4.1 (on NEXTSTEP) Questions
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu

We are trying to get postgres to work on NEXTSTEP 3.0 on m68k  
hardware.

We have running:
	sysv ipc and shared memory
	dynamic loader
Postgres passes:
	regress
	demo
Postgres does not pass:
	video
Q1: Should postgres 4.1 be able to run the video test?

Q2: Postgres backend uses different id's for it's sysv semaphores.  
That makes those semaphores pretty useless when synchronizing. It  
uses 1 semaphore and the rest is done with test-and-set. Is this  
meant to be so, if yes, what is the meaning of this setup?

---
Tom Hageman      tom@icce.rug.nl    Tel. (+31) 50 718469
Gerben Wierda    [NeRD:7539]        Tel. (+31) 35 833539
  "If you don't know where you are going, any road will 

  take you there." From the Talmud(?), rephrased in 

  Lewis Carroll, "Alice in Wonderland".