Hi, On 2018-06-19 10:26:26 -0300, Matheus de Oliveira wrote: > Hello friends. > > On Tue, Jun 12, 2018 at 3:31 PM, Andres Freund <and...@anarazel.de> wrote: > > > > > On 2018-06-11 17:39:14 -0700, Andres Freund wrote: > > > I plan to go over the change again tomorrow, and then push. Unless > > > somebody has comments before then, obviously. > > > > Done. > > > > > Sorry to bother about this, but do you have any plan to do the minor > release before planned due to this bug?
Unclear at this point. There's been discussion about it, without coming to a conclusion. > I'm pondering what is the best option to avoid a forced shutdown of this > server: > - should I just wait for a release (if it is soon, I would be fine)? > - build PG from the git version by myself? > - or is there a safer workaround to the problem? (not clear to me if > deleting the `global/pg_internal.init` file is really the way to go, and > the details, is it safe? Should I stop the server, delete, start?) You should first make sure it's actually this problem - which tables are holding back the xmin horizon? After that, yes, deleting the global/pg_internal.init file is the way to go, and I can't think of a case where it's problematic, even without stopping the server. Greetings, Andres Freund
