Re: PostgreSQL binaries under /usr/lib, why?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/22/2013 12:40 PM, Stuart Bishop wrote:
> On Fri, Feb 22, 2013 at 4:41 PM, Rafael Martinez
> <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> wrote:

>> According to FHS-2.3, /usr/lib includes object files, libraries,
>> and internal binaries that are not intended to be executed
>> directly by users or shell scripts.
>
> Right. This is why wrappers are installed in /usr/bin that invoke
> the correct version of the executable when it is known (and a
> default version when it isn't, such as when you are connecting to a
> remote server). You shouldn't need to invoke anything from /usr/lib
> directly, unless you are doing something particularly low level.
>

Thanks for the information.

The confusion occurs because not all binaries installed by postgres
packages are available via /usr/bin and wrappers.

i.e. pgbench, pg_archivecleanup, pg_upgrade, initdb and several others
are not available via /usr/bin and they should not be defined as low
level.

Having *all* binaries installed by a postgres package accessible via
/usr/bin and wrappers would make live easier for many users.

regards,
- --
Rafael Martinez Guerrero
Center for Information Technology
University of Oslo, Norway

PGP Public Key: http://folk.uio.no/rafael/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlEnXrUACgkQBhuKQurGihRk/ACfZdx4LkqDx5oMMJB6zvyNsY1w
3IsAn3Wkq2+1cpTTQCni4aN7sMJMc03n
=jXN7
-----END PGP SIGNATURE-----