Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace
От | Michael Paquier |
---|---|
Тема | Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace |
Дата | |
Msg-id | CAB7nPqS7aqnrPqgsrhMuOi2a8NYv4UPqKZvzq=GsU=nFUOmZug@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] pg_upgrade fails when postgres/template1 isn't in default tablespace (Marti Raudsepp <marti@juffo.org>) |
Ответы |
Re: [PATCH] pg_upgrade fails when postgres/template1 isn't
in default tablespace
|
Список | pgsql-hackers |
On Mon, Jul 20, 2015 at 4:31 PM, Marti Raudsepp <marti@juffo.org> wrote: > On Mon, Jun 22, 2015 at 9:20 PM, Robert Haas <robertmhaas@gmail.com> wrote: >> On Fri, Jun 19, 2015 at 12:10 PM, Marti Raudsepp <marti@juffo.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
В списке pgsql-hackers по дате отправления: