Re: [GENERAL] Compatibility of libpg
От | Magnus Hagander |
---|---|
Тема | Re: [GENERAL] Compatibility of libpg |
Дата | |
Msg-id | CABUevEx2iCgY5XHSF_==6E=J7p3r8AVhBxcNO8EVtSP4oX9JjQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] Compatibility of libpg (John R Pierce <pierce@hogranch.com>) |
Список | pgsql-general |
On Thu, May 4, 2017 at 7:32 PM, John R Pierce <pierce@hogranch.com> wrote:
On 5/4/2017 2:19 AM, Magnus Hagander wrote:On Wed, May 3, 2017 at 11:31 PM, John R Pierce <pierce@hogranch.com> wrote:On 5/3/2017 2:20 PM, Magnus Hagander wrote:
Please note that this method of building libpq has been removed from Postgres 10, so it's considered to be deprecated for quite some time.
this page https://www.postgresql.org/docs/current/static/install-windo ws-libpq.html probably should be updated then. That page is completely gone in version 10. If you look at https://www.postgresql.org/docs/devel/static/install- windows.html you will notice the entire 17.2 section has been removed, as well as the text on the root page referring to it.
well, dropped in the latest not-yet-released version doesn't really make it 'deprecated for quite some time'. if this has been the long term intention, the docs should have reflected this some revisions back.
True. The fact that the reported issue has been around for a very long time without anybody caring to fix it is though.
I still think the Windows packagers (<cough>EnterpriseDB</cough>) should have a client-only package which has options to just install the libs, or the libs + client utils (psql, pg_dump/restore/dumpall and optionally pg_admin). I realize that this wouldn't be /that/ much smaller than the whole 9 yards, but its a psychological thing for the end user, they think of the server as 'heavy', also would be good for automated client deployments in business envirnoments.
That's a different thing though, and I agree that this would be useful.
В списке pgsql-general по дате отправления: