Thanks Dmitriy, It turns out the solution I used was to su to postgres in Linux, and then run the command psql without arguments, at which time I could have my way with any object. More in my responses to you... On Sunday 16 January 2011 06:21:28 Dmitriy Igrishin wrote: > Hey Steve, > > 2011/1/16 Steve Litt <slitt@xxxxxxxxxxxxxxxxxxx> > > > Hi all, > > > > I've somehow messed up something. > > > > psql super > > psql's synopsis is > psql [option...] [dbname [username]] > Thus, the call "psql super" connects psql to a database > "super" but since username unspecified it is connected > with current Unix user (which is returned by whois(1)). > > So, you should call psql like that > psql super super slitt@mydesk:~$ psql super super psql: FATAL: Ident authentication failed for user "super" slitt@mydesk:~$ psql postgres postgres psql: FATAL: Ident authentication failed for user "postgres" slitt@mydesk:~$ > or like that > psql -U super slitt@mydesk:~$ psql -U super psql: FATAL: Ident authentication failed for user "super" slitt@mydesk:~$ psql -U postgres psql: FATAL: Ident authentication failed for user "postgres" slitt@mydesk:~$ Now watch this: slitt@mydesk:~$ su - postgres Password: postgres@mydesk:~$ psql -U postgres psql (8.4.5) Type "help" for help. postgres=# Luckily for me, needing to be Linux user postgres isn't at all an inconvenience, so the problem is pretty much solved, although some curiosity remains. Thanks SteveT Steve Litt Recession Relief Package http://www.recession-relief.US Twitter: http://www.twitter.com/stevelitt -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
