Re: [PATCH] pg_regress and non-default unix socket path

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Christoph Berg <cb(at)df7cb(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pg_regress and non-default unix socket path
Date: 2013-04-12 15:13:59
Message-ID: CA+TgmobiZchpgs_gYmgxvWrzxC2ccnn+tPLNfjvK-8D4di0=dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 9, 2013 at 8:08 AM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
> Debian has been patching pg_regress for years because our default unix
> socket directory is /var/run/postgresql, but that is not writable by
> the build user at build time. This used to be a pretty ugly "make-
> patch-make check-unpatch-make install" patch dance, but now it is a
> pretty patch that makes pg_regress accept --host=/tmp.
>
> The patch is already part of the .deb files on apt.postgresql.org and
> passes all regression test suites there.
>
> Please consider it for 9.3. (And maybe backpatch it all the way...)

The hunk that changes the messages might need some thought so that it
doesn't cause a translation regression. But in general I see no
reason not to do this before we release beta1. It seems safe enough,
and changes that reduce the need for packagers to carry private
patches are, I think, generally a good thing.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robins Tharakan 2013-04-12 15:14:02 How to use EXPLAIN (TIMING)
Previous Message Tom Lane 2013-04-12 14:58:13 Re: Analyzing bug 8049