| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove readline notice from psql --version? |
| Date: | 2012-05-21 03:18:00 |
| Message-ID: | 1337570088-sup-1035@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lane's message of dom may 20 23:04:59 -0400 2012:
>
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Excerpts from David Fetter's message of dom may 20 15:30:52 -0400 2012:
> >> I think this should be replaced with a notice about the actual library
> >> used.
>
> > That was my thought as well, but is it possible to implement it?
>
> And, more to the point, would it be more reliable than checking the
> results of system-specific tools such as ldd?
If well implemented, my guess is that it would be. For example recall
that in Debian they are shipping psql linked to libedit due to licensing
concerns, but then suggest a hack to use LD_PRELOAD to load libreadline
instead. So ldd might tell you that it's linked to libedit and fail to
notice that at runtime something different is being used.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-21 04:02:25 | Re: Remove readline notice from psql --version? |
| Previous Message | Daniel Farina | 2012-05-21 03:06:08 | Re: Schema version management |