Connecting to PostGreSQL on same machine: Mac OSX

[Sivakatirswami]

Success, sort of -;)

Even though trying to start up with
/usr/local/pgsql/bin/pg_ctl/ -D /usr/local/pgsql/data -l logfile restart

fails...

> postgres$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data

works and I can connect now with Revolution... obviously because we 
changed the postgresql.conf tcpip setting to "true"    great!... And

  if I quit my shell sesson and open a new one I can immediately

% su postgres
./psql katir_test
and I get

Welcome to psql 7.4.5, the PostgreSQL interactive terminal.
etc...

I'm up and running in console mode as well... ;-)

but,

a)  I'm not sure if there are hidden issues that will be problematic 
later because I did not restart the server with pg_ctl and
b) this work around (booting the postmaster instead of running pg_ctl) 
begs the question of why

katir:~ postgres$ /usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data 
-l logfile restart

fails...

Sivakatirswami








On Dec 13, 2004, at 9:03 AM, Sivakatirswami wrote:

> More on this...
>
> I can start the dbase in the foreground..
>
> katir:~ postgres$ /usr/local/pgsql/bin/postmaster -D 
> /usr/local/pgsql/data
> LOG:  database system was shut down at 2004-12-13 08:56:00 HST
> LOG:  checkpoint record is at 0/9E0780
> LOG:  redo record is at 0/9E0780; undo record is at 0/0; shutdown TRUE
> LOG:  next transaction ID: 551; next OID: 17153
> LOG:  database system is ready
>
> I see three postgres processes now in the activity monitor... but I 
> can't find a way to issue commands to it from the cmd line.. there is 
> no prompt after the last line above.
>
>
>
>> but
>
>
>> katir:~ postgres$ /usr/local/pgsql/bin/pg_ctl -D 
>> /usr/local/pgsql/data -l logfile restart
>
> doesn't work.. see below.
>
>
>
> On Dec 13, 2004, at 8:45 AM, Sivakatirswami wrote:
>
>> Frank, thanks for your patient responses
>>
>> Still no go..
>>
>> katir:~ postgres$ /usr/local/pgsql/bin/pg_ctl -D 
>> /usr/local/pgsql/data -l logfile restart
>>
>> nothing happens, activity monitor doesn't show any start postgres 
>> processes started.
>>
>> So, I'm stumped at this moment.
>>
>> Is there some other log that will tell give us any useful feed back 
>> on what is happening.
>>
>> Pierre:  Yes, I suppose I could  do a complete re-install, but, since 
>> two days ago I *was* able to start the server and all that I did in 
>> the interim was to "touch" the pg_hba.conf and postgresql.conf files, 
>> I *really* would like to fix this "manually" so that I get a grip on 
>> the issues and not simply "quit" and start over again.  though, if 
>> there is no definitive diagnostic then I may have not choice...
>>
>>
>> In the meantime I'm logging into our new server in Connecticutt where 
>> Postgres is running just fine and going through the tutorials via 
>> ssh...  creating test data bases and doing my "homework." (I'll have 
>> more to ask you about the rev ap server you installed after I get a 
>> little deeper into it...)
>>
>> So, not having it running on my own machine is not a show stopper, 
>> just a nuisance.. normally I would be doing this kind of  R & D 
>> during hours when I am off line... now I have to do it during on-line 
>> hours= "eats my day job time." i.e. the time when I should be working 
>> on web design, content and team coordination etc.
>>
>> Pierre, perhaps you could email me off list your own pg_hba.conf and 
>> postgresql.conf files that you are using on your OSX machine, I would 
>> install those and see if it works
>>
>> Thanks!
>> Sivakatirswami
>> Himalayan Academy Publications
>> at Kauai's Hindu Monastery
>> katir at hindu.org
>>
>> www.HimalayanAcademy.com,
>> www.HinduismToday.com
>> www.Gurudeva.org
>> www.Hindu.org
>>
>> On Dec 13, 2004, at 7:18 AM, Frank D. Engel, Jr. wrote:
>>
>>> This is trying to connect to PostgreSQL through a UNIX domain socket 
>>> rather than TCP/IP.  This should still be working, but if not, try a 
>>> command like this:
>>>
>>> psql -h <hostname> -U <username> dbname
>>>
>>>
>>>>
>>>> So, no I cannot even start up the server at all.
>>>
>>> Did you check the activity monitor again to see if it was running or 
>>> not?  The above given error message is a connectivity problem, any 
>>> does not necessarily mean that the server is not running.
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>