[Akonadi] [Bug 286826] After system crash, postgresql akonadi server doesn't start due to lock file

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=286826

Daniel Vrátil <dvratil at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
   Version Fixed In|                            |1.12.2
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/akon
                   |                            |adi/f217d9e96dc8de88916e8ca
                   |                            |0b93dd9a7500bbbc3

--- Comment #2 from Daniel Vrátil <dvratil at redhat.com> ---
Git commit f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3 by Dan Vrátil.
Committed on 06/05/2014 at 14:38.
Pushed by dvratil into branch '1.12'.

Fix PostgreSQL start when postmaster.pid is not removed after non-clean
shutdown

When PostgreSQL is not terminated nicely, a pidfile is left behind in db_data,
which will prevent pg_ctl from starting a new PostgreSQL server.

We check for postmaster.pid file and verify that postgres server with PID
specified in the pidfile is not running anymore, then delete the pidfile to
allow pg_ctl to start a new server. If the postgres server is still running
(possibly after Akonadi server crash), we try to connect to it right away.
FIXED-IN: 1.12.2

M  +37   -0    server/src/storage/dbconfigpostgresql.cpp

http://commits.kde.org/akonadi/f217d9e96dc8de88916e8ca0b93dd9a7500bbbc3

-- 
You are receiving this mail because:
You are the assignee for the bug.