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

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

On Mon, Jul 20, 2015 at 4:31 PM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
> On Mon, Jun 22, 2015 at 9:20 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Fri, Jun 19, 2015 at 12:10 PM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>>> One of my databases failed to upgrade successfully and produced this error
>>> in the copying phase:
>>>
>>> error while copying relation "pg_catalog.pg_largeobject"
>>> ("/srv/ssd/PG_9.3_201306121/1/12023" to "/PG_9.4_201409291/1/12130"): No
>>> such file or directory
>
>> I haven't looked at the patch, but this seems like a good thing to
>> fix. Hopefully Bruce will take a look soon.
>
> Ping? This has gone a month without a reply.
>
> Should I add this patch to a commitfest? (I was under the impression
> that bugfixes don't normally go through the commitfest process)

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".
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Beena Emerson 2015-07-20 12:59:36 Re: Support for N synchronous standby servers - take 2
Previous Message Alexander Korotkov 2015-07-20 12:18:12 Use pg_rewind when target timeline was switched