I'm trying to reinstall Postgresql on my Mac (running 10.3.2) and
running into bizarre things that I haven't experienced before.
Anyone here know anything about running Postgresql on the OS X
platform?

The latest issue I'm having is that I'm trying to run createdb to
create the test database. Here's the error message:

Computer:~ postgres$ /usr/local/bin/createdb test
createdb: could not connect to database template1: could not connect
to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
Lola-Lees-Computer:~ postgres$

Yes, server is running (I have the startup script loaded in the
/Library/Startup folder), far as I can tell.

I'm using the Liyange package from http://www.entropy.ch, if this helps.

--

Lola - mailto:lola (AT) his (DOT) com
http://www.lolajl.net | Blog at http://www.lolajl.net/blog/
I'm in Bowie, MD, USA, halfway between DC and Annapolis.



---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

Lola Lee <lola (AT) his (DOT) com> writes:
It works fine (I use it regularly).

Evidently not. You'll need to go find out why it didn't start.
One likely possibility is that shared_buffers and related parameters
are set too high --- by default, OS X has a pretty tight limit on
the size of shared-memory requests, and it's easy to exceed it.

I don't know where that package puts the postmaster's error output,
but that is what you should look for.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

Hi Lola,

Note that on Marc Liyanage's page there is a link for
troubleshooting. If you follow it you'll find instructions on how to
set some system parameters on Mac OS X if this is the particular
problem you're having.

You may always repeat the procedure Marc Liyanage describes until you
get it right (if you're the cause ;-), it can't do harm.

I'm working on a GUI double-clickable PostgreSQL installer for OS X
but this project is not a top priority right now for me. When it's
done I'll let the list know.

OS X is great for PostgreSQL. I've been running 7.3 on Jaguar and
now I have 7.4 on Panther, all installed with Marc Liyanages packages.

Cheers,

Marc

PS: for some pgsql tools for OS X look at http://aliacta.com/products.

At 3:56 PM -0500 3/6/04, Tom Lane wrote:

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

Tonight I got my first pgsql server up and running on a G5. Because I
encountered similar "problems" I think this might be of help
(hopefully):

I installed the db from scratch and installed it into /usr/local/pgsql
(the binaries as well). As far as I can tell, Marc Lyanage's install
differs slightly from that because it uses /usr/local/bin for the pgsql
binaries. If I were you I'd open the Startup item in any texteditor
like so:

sudo pico /Library/StartupItems/PostgreSQL/PostgreSQL and check the
line that looks like this:

su - postgres -c '/usr/local/pgsql/bin/pg_ctl start -D
/usr/local/pgsql/data -l /usr/local/pgsql/logfile -o -i'

Make sure all paths are correct and - in case your postgres user
doesn't have a home directory, try to leave out the "-" right after
sudo so that it reads:

su postgres -c '/usr/local/pgsql/bin/pg_ctl start -D
/usr/local/pgsql/data -l /usr/local/pgsql/logfile -o -i'

This solved my problems that I had. Plus, I changed the location of the
logfile (because my postgres user could write to that /ur/local/ppgsq
dir but I like to keep the log together in the data dir) so that my
line reads:

su postgres -c '/usr/local/pgsql/bin/pg_ctl start -D
/usr/local/pgsql/data -l /usr/local/pgsql/data/logfile -o -i'


Hope this helped...
Anyway, I found that a system reboot often solved a problem or two (but
don't do it in a production environment, you'll get killed ;-))

Stephan


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster