Re: Hokey wrong versions of libpq in apt.postgresql.org

On 08/12/2014 10:26 AM, Steve Crawford wrote:
>
> On 08/07/2014 04:30 PM, Joshua D. Drake wrote:
>>
>> Hello,
>>
>> I know this has been brought up before:
>>
>> http://www.postgresql.org/message-id/20140724080902.GA28113@msg.df7cb.de
>
> For reference, libpq and packaging issues discussed here as well:
> http://www.postgresql.org/message-id/53A304BC.40908@pinpointresearch.com
> http://www.postgresql.org/message-id/53989C91.6050403@pinpointresearch.com
>
>>
>> But this is just plain wrong. I don't care that the FAQ (on the wiki)
>> says we are doing it wrong for good reasons. When I (or anyone else)
>> pulls postgresql-$version-dev, I want the libpq for my version. I do
>> not want 9.3.

I am finally able to get back around to this and I am still calling:
Hokey. I just loaded up a fresh precise (I assume trusty will act the
same way) and installed postgresql. I installed it, without the PDGD
repository and everything worked perfectly. The only error I got when
using pgxnclient to install pg_repack was an error about not having
libedit-dev installed. I installed it, and it was perfect. I even tested
with create extension etc...

So... If we are supposed to ship the "latest" lib... how come Debian or
Ubuntu don't do that? They ship the latest lib for the version they are
shipping and because of that, everything works, as expected.

I iterate, the current apt.postgresql.org is not doing things correctly.
It breaks things and it shouldn't.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
"If we send our children to Caesar for their education, we should
not be surprised when they come back as Romans."