Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace
Date: 2015-07-22 14:00:17
Message-ID: CA+TgmoZNqei+x--rfdvpFfuSmyc+Ky5atRDjbrn9XTTQk=LV=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 20, 2015 at 8:20 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> After a certain amount of time without anything happening, I would
> recommend just adding it to a CF to have it get attention. I imagine
> that it is one of the reasons why there is as well a category "Bug
> Fix".

+1. I would recommend adding it to the CF *immediately* to have it
get attention. The CF app is basically our patch tracker.

--
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 Robert Haas 2015-07-22 14:15:19 Re: [PROPOSAL] VACUUM Progress Checker.
Previous Message Robert Haas 2015-07-22 13:59:23 Re: optimizing vacuum truncation scans