Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA12623; Mon, 30 Mar 92 11:09:45 -0800
Message-Id: <9203301909.AA12623@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: Remote Operation
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Mon, 16 Mar 92 08:39:20 PST."
             <9203161639.AA18645@postgres.Berkeley.EDU> 
Date: Mon, 30 Mar 92 11:09:22 PST

you write:
> Hi, Jaff
> 
> 	When I run postgres as user postgres on remote machine
> through the local network, everything goes fine. But as one of the 
> user, when I run on remote machine, it give me following message :
> 
> chenyy@loony:/tmp_mnt/home/dweezil/postgres/demo
> -------16%createdb mydemo2
> FATAL 1:Mar 16 11:04:12:process userid (345) != database owner (79)
> 
> /home/dweezil/postgres/bin/createdb: database creation failed on mydemo2.

This particular message occurs only when the effective userid of the backend
(which due to the setuid permissions on the installed binaries should be
postgres) is not the same as postgres' userid.

Make sure that the binaries are owned by postgres and are setuid to owner.

It sounds like you may have nfs mounted the file system where postgres is
installed and are trying to run on a different machine than where the binaries
actually live.  If this is the case you should run the postmaster only on the
server, and only run front-ends on the remote machine (setenv PGHOST to be the
server machine).


Jeff Meredith
mer@postgres.berkeley.edu