Hello people,
My initdb problem has been solved (PostgreSQL 8.2.4, Mac OS
X 10.3.9). I thought I would post a brief summary, but first
I'd like to thank everyone on this list who so kindly and
generously made suggestions. I'd particularly like to thank
Sean Dooley <[EMAIL PROTECTED]>, who assisted
Tom Lane <[EMAIL PROTECTED]> wrote:
Joe Barwell <[EMAIL PROTECTED]> writes:
> I get the same result trying to initdb after rebooting,
the
> end of which is:
> /Library/PostgreSQL8/data/base/1 ... FATAL: could not
> create shared memory segment: Cannot allocate memory
> DETAIL: Failed system call
John DeSoi <[EMAIL PROTECTED]> wrote:
>This has got to be the longest thread ever to get
PostgreSQL running
on the Mac -- but I'm glad you have not given up :).
Hi John,
Partly it's because I don't have much time to spend
investigating this, partly it's a very positive reflection
of the great wi
Hi Joe,
This has got to be the longest thread ever to get PostgreSQL running
on the Mac -- but I'm glad you have not given up :).
On Jun 21, 2007, at 12:49 AM, Joe Barwell wrote:
acorn$ sudo su postgres -c 'pg_ctl start -l logfile -D
/Library/PostgreSQL8/data'
Password:
sh: line 1: logfile:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Doesn't MacOSX install postgresql by default for one of their management
> services?
Good point --- IIRC, there is a PG 7.3.something embedded in Apple
Remote Desktop. I'm not sure whether it starts automatically on boot;
I seem to recall a recent
Tom Lane wrote:
Joe Barwell <[EMAIL PROTECTED]> writes:
I get the same result trying to initdb after rebooting, the
end of which is:
/Library/PostgreSQL8/data/base/1 ... FATAL: could not
create shared memory segment: Cannot allocate memory
DETAIL: Failed system call was shmget(key=2, size=164
Joe Barwell <[EMAIL PROTECTED]> writes:
> I get the same result trying to initdb after rebooting, the
> end of which is:
> /Library/PostgreSQL8/data/base/1 ... FATAL: could not
> create shared memory segment: Cannot allocate memory
> DETAIL: Failed system call was shmget(key=2, size=1646592,
> 0
Tom Lane <[EMAIL PROTECTED]> wrote:
> Ugh. I don't recall exactly when Apple got around to
> including ipcs, but I guess it wasn't in 10.3.9. Your
> problem is that you're flying blind because you cannot
> tell what's going on in shared memory.
>
> What I suspect is that there's an unused shared
Joe Barwell <[EMAIL PROTECTED]> writes:
> acorn$ sysctl -a | grep shm
> kern.sysv.shmmax: 4194304
> kern.sysv.shmmin: 1
> kern.sysv.shmmni: 32
> kern.sysv.shmseg: 8
> kern.sysv.shmall: 1024
OK, so you should be able to do 4MB without problems.
> acorn$ sudo ipcs -a
> Password:
> sudo: ipcs: comma
Hi Tom,
acorn$ sysctl -a | grep shm
kern.sysv.shmmax: 4194304
kern.sysv.shmmin: 1
kern.sysv.shmmni: 32
kern.sysv.shmseg: 8
kern.sysv.shmall: 1024
acorn$ sudo ipcs -a
Password:
sudo: ipcs: command not found
> Also, which OSX release is this again?
10.3.9 on a g4.
Joe
--
Joe Barwell <[EMAIL PROTECTED]> writes:
> Fixing the postgres user's home may have been an
> improvement, but now I get problems with the shared memory
> segment:
Hmm ... Apple's default for SHMMAX is definitely penurious, but it's not
so small that PG shouldn't be able to start at all. What do y
Hello people,
Fixing the postgres user's home may have been an
improvement, but now I get problems with the shared memory
segment:
acorn$ sudo su postgres -c 'initdb -D
/Library/PostgreSQL8/data'
Password:
The files belonging to this database system will be owned by
user "postgres".
This user mus
Joe Barwell <[EMAIL PROTECTED]> writes:
> The following, however, makes me suspect it's still a
> problem with initdb:
> acorn$ postgres
> postgres cannot access the server configuration file
> "/Library/PostgreSQL8/data:/postgresql.conf": No such file
> or directory
What's that colon doing in th
EMAIL PROTECTED] On Behalf Of Joe Barwell
Sent: Thursday, 21 June 2007 14:50
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] initdb problem
acorn$ sudo su postgres -c 'pg_ctl start -l logfile -D
/Library/PostgreSQL8/data'
Password:
sh: line 1: logfile: Permission denied
server
"Phillip Smith" <[EMAIL PROTECTED]> wrote:
> My bad - is has the shell, but as you say, the home
> directory is /dev/null
>
> niutil -destroyval -u admin . /users/postgres home
> /dev/null niutil -appendprop -u admin . /users/postgres
> home /Library/postgreSQL8
>
> Once again, use at your own ris
My bad - is has the shell, but as you say, the home directory is /dev/null
NOW, I must preface this with a warning saying that I have NOT tested this,
and do not guarantee that it will work. I found it on a Mac forum and have
never tried it, or seen confirmation that it will work. Follow on at you
Hello People,
My thanks to the several people who gave suggestions for how
to solve my initdb problem.
1. "Phillip Smith" <[EMAIL PROTECTED]>
suggested the problems stemmed from:
the 'postgres' user not having a correct shell login setup.
It looks like the home directory is set to /dev/null whic
PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of James Herbers
Sent: Tuesday, June 19, 2007 9:11 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] initdb problem
No MAC expert but try this when changing to the postgres user:
su - postgres
the hyphen gives you an environment for the postgres
r to have a proper login shell
(/bin/bash maybe?) but I specifically avoid Mac's so that's about all I can
tell you. B)
Cheers,
~p
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of James Herbers
Sent: Wednesday, 20 June 2007 11:11
To: pgsql-admin@po
No MAC expert but try this when changing to the postgres user:
su - postgres
the hyphen gives you an environment for the postgres user.
J. Herbers
Quoting Joe Barwell <[EMAIL PROTECTED]>:
Hello people,
Having installed the universal binary for pg 8.2.4 on my mac
running 10.3.9, I'm now try
kalyanaraman rajaraman <[EMAIL PROTECTED]> writes:
> -bash-3.00$ initdb -D /var/lib/pgsql/data -W template1
> The files belonging to this database system will be
> owned by user "postgres".
> This user must also own the server process.
> The database cluster will be initialized with locale
> ta_IN.
Harry wrote:
> creating template1 database in
> /usr/local/postgresql7.4.1/data/base/1... DEBUG:
> invoking IpcMemoryCreate(size=1081344)
> FATAL: could not create shared memory segment: Function not
> implemented DETAIL: Failed system call was shmget(key=1,
> size=1081344, 03600). DEBUG: proc_
Robert wrote:
> creating template1 database in /usr/shared/postgresql/data/base/1...
> FATAL: invalid value for parameter "lc_messages": "3079"
Perhaps you should set your locale environment to something less
bizarre.
---(end of broadcast)---
TIP
ot; <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "Andy Callan" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 3:58 PM
Subject: Re: [ADMIN] initdb problem
> On Thu, 2003-09-18 at 09:25, Jaskier wrote:
> > Hi,
> >
> > No it will not work, You have
On Thu, 2003-09-18 at 09:25, Jaskier wrote:
> Hi,
>
> No it will not work, You have to be owner, or have full access to this
> directory. Also you should, I think this is necessary to run Initdb as a
> Postgres user.
It can't be run as root, but it can be run as any other user. The key is
that wh
Hi,
No it will not work, You have to be owner, or have full access to this
directory. Also you should, I think this is necessary to run Initdb as a
Postgres user.
This is what you have to do:
As root change rights to this /usr/local/pgsql and change the owner (it
would be better) to Postgres
The
On Mon, 25 May 1998, Dany K. wrote:
> Hi everybody,
>
> I just downloaded and installed the new PostgreSQL 6.3.2. Everything went
> fine including the installation.
> Now my problem: When i run "initdb", the following error message appears :
>
>
27 matches
Mail list logo
