| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade + Ubuntu |
| Date: | 2015-07-10 19:10:33 |
| Message-ID: | 20150710191033.GC7382@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
>
> On 07/10/2015 11:01 AM, Mike Blackwell wrote:
> >Does pg_config show the correct location? If so, perhaps pg_upgrade
> >could get the .conf location the same way rather than requiring a
> >command line option.
>
> Good idea but:
>
> postgres(at)ly19:~$ pg_config
> You need to install postgresql-server-dev-X.Y for building a server-side
> extension or libpq-dev for building a client-side application.
>
> Which is worse having to install yet another package or having a command
> line option?
It seems to me that this is a Debian packaging issue, not an upstream
issue, isn't it? If you want to fix the problem in this way, then
surely whatever package contains pg_upgrade should also contain
pg_config.
Why are you not using pg_upgradecluster anyway? There's a mode to use
pg_upgrade there.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Blackwell | 2015-07-10 19:20:04 | Re: pg_upgrade + Ubuntu |
| Previous Message | Peter Geoghegan | 2015-07-10 18:56:11 | Re: Minor issue with BRIN regression tests |