On Sunday 16 January 2011 1:49:43 pm Steve Litt wrote: > On Sunday 16 January 2011 16:02:12 Raymond O'Donnell wrote: > > If you have configured PG to listen on a TCP/IP port (5432 by default), > > you can also do: > > > > psql -U postgres -h localhost super > > > > Ray. > > Thanks Ray, > > You were sooooo close! The command that works is this: > > psql -U super -h localhost super > > That's because the super database is owned by the super user, in this > particular case. Interestingly enough, even though I've set my port to be > 5433 instead of 5432, it wasn't necessary for me to add -p 5433. Just realized you do have a server running at 5433 per this from one of your previous posts: slitt@mydesk:~$ psql -U postgres -h localhost -p 5433 super Password for user postgres: psql: FATAL: password authentication failed for user "postgres" FATAL: password authentication failed for user "postgres" slitt@mydesk:~$ There would have been a different error if there was no server listening on that port. It would seem you have more than one Postgres server running. > > Your method has the big benefit of being able to supervise from a Postgres > Superuser who doesn't have a Linux account (super, in this case). Thanks > for the info! > > SteveT > > Steve Litt > Recession Relief Package > http://www.recession-relief.US > Twitter: http://www.twitter.com/stevelitt -- Adrian Klaver adrian.klaver@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
