ACPI administration advocacy advocacy advocacy opinion alsa amarok apache apple apt aptitude audio audo authentication automount avi awk bash BIOS boot business cache calendar calibre cdr cdrecord censorship commandline computerscience console convert cron cut database date debian degree design desktop development disk dpkg dvd economics education emacs email europe exim faad ffmpeg file files firefox firewall flash foss freedom ftp fun fuse git gnumeric graphics grep growisofs grub gtkpod hardware hardware html idiocy image imagemagick images installation ip iphone ipod iptables iso itunes ivman kde kernel keyboard knoppix lame laptop latex linux locale lockin longlines m4a microsoft mimetypes minitab mount mp3 mp4 mplayer multimedia music mysql network nfs nfs4 nmap openbox openoffice opinion opinion partition pdf perl php politics postgresql printing privacy programming rant remote rhythmbox rss rsync rxvt scp screengrab screenshot script scripting scsi security sed server shell siteadmin sitenews sitesoftware skype skype slackware sound sox spam spreadsheet ssh statistics subversion sudo svk swap t23 t43 terminal text thinkpad thunderbird time timezone ubuntu udev upgrade usb usbmount users uuid versioncontrol vfat video vnc windows wine wordpress wordprocessing X40 xwindows xwindows youtube
One of the most annoying things is the way that postgres is first installed. IDENT authentication requires your unix and postgres identities to be the same. It's very frustrating and means we often end up with this error: FATAL: IDENT authentication failed for user
.A way to fix this, at least on development machines is to tell postgres to trust all local users. In pg_hba.conf put something like this. It is apparently the "upstream" default and allows unrestricted access to any database by any user on the local machine:
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD # local all all trust # IPv4-style local connections: host all all 127.0.0.1 255.255.255.255 trust
what if after changing pg_hba to md5 or trust it still tries ident auth? what could still be wrong?
i've solved this problem by adding the following line : local all user md5 before: local all all ident sameuser
in my pg_hba.conf. I think it's more elegant and secure solution. thanks.
Posted by milo on 2011-04-19 08:22:42.