From: | John DeSoi <desoi(at)pgedit(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org> |
Subject: | .bash_profile replaced on software updates |
Date: | 2016-05-21 14:09:13 |
Message-ID: | 78C27D42-3419-4DE7-A8E4-B79588703F45@pgedit.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm using CentOS and updating Postgres with yum. Whenever Postgres is updated (even minor updates) the .bash_profile is replaced with the lines below. I was happy to see the idea of the .psql_profile added fairly recently, but I don't understand why the last line is commented out. I still have to remember to uncomment the last line in this file every time I update Postgres which seems to defeat the purpose.
The reason I need .pgsql_profile is that lots of useful Postgres executables (e.g. pg_archivecleanup) are not in the postgres path. Does everyone just use the full path name and change this in the configuration file for major updates?
[ -f /etc/profile ] && source /etc/profile
PGDATA=/var/lib/pgsql/9.5/data
export PGDATA
# If you want to customize your settings,
# Use the file below. This is not overridden
# by the RPMS.
#[ -f /var/lib/pgsql/.pgsql_profile ] && source /var/lib/pgsql/.pgsql_profile
John DeSoi, Ph.D.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-05-21 15:10:57 | Re: .bash_profile replaced on software updates |
Previous Message | Tom Lane | 2016-05-21 14:01:22 | Re: How to know if SPI or some other API triggered an ERROR. |