Conversation

Notices

1. musicman (musicman@nu.federati.net)'s status on Monday, 02-Nov-2020 15:49:12 EST musicman
   If anybody is on diaspora and knows #postgresql, would love it if you took a look at this issue: https://joindiaspora.com/posts/19344936
   
   It might be a systemd issue, but I am using the official yum repo on Postgres 12, not postgres 13, and not doing anything fancy with systemd, so I doubt it.
   1. lnxw48a1 (lnxw48a1@nu.federati.net)'s status on Monday, 02-Nov-2020 20:13:08 EST lnxw48a1

      in reply to
      @musicman I see that you've resolved it. Did you have to do anything special, or did it just take a long time to start working?
      
      If you're using screen, try "CTRL+A C" and run "systemctl status postgresql-12" to see where it is in the start / restart process. (If you're using tmux, replace CTRL+A with CTRL+B. I haven't used dtach in a while, so I don't recall what command it uses.)
      1. musicman (musicman@nu.federati.net)'s status on Tuesday, 03-Nov-2020 10:24:12 EST musicman

         in reply to
         I think this is a bug, but whether in systemd or postgres, I am not sure.
         
         Basically, postgres starts, but replication fails. It is going to fail forever (I think), but systemctl never figures it out.
         
         I should look to see if this is already filed.