[Kde-pim] Review Request 113909: Revisit the PostgreSQL dbconfig

Dan Vrátil dvratil at redhat.com
Mon Jan 13 13:02:37 GMT 2014


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/113909/#review47313
-----------------------------------------------------------



server/src/storage/dbconfigpostgresql.cpp
<https://git.reviewboard.kde.org/r/113909/#comment33704>

    I just realized this won't work: mDatabaseProcess holds the pg_ctl QProcess which has ended long time ago, so mDatabaseProcess->waitForFinished() will always return FALSE and fall through all the kill methods.
    
    We should probably run pg_ctl stop --pgdata=XXX --mode=fast -w --timeout=3 and wait for *this* QProcess to terminate, then fallback to IMMEDIATE etc.
    
    The IMMEDIATE shutdown is broken the same way.
    


- Dan Vrátil


On Nov. 17, 2013, 6:55 p.m., Cédric  Villemain wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/113909/
> -----------------------------------------------------------
> 
> (Updated Nov. 17, 2013, 6:55 p.m.)
> 
> 
> Review request for Akonadi.
> 
> 
> Repository: akonadi
> 
> 
> Description
> -------
> 
>     Remove defaultCleanShutdownCommand setting, this used to contain a mix of
>     command and parameters. I kept only the PGDATA in mPgData (new setting).
>     
>     Use the socketDir defined by mHostName (Host setting), set by init() when using
>     an internal server, instead of building the path each time its required.
>     
>     Cosmetic: expand command arguments to longer ones when possible
>               "-D" -> "--pgdata"
>               Change star to 1 in database query check
>               "SELECT *" --> "SELECT 1"
>     
>     Remove PostgreSQL configuration file management, we use the command arguments
>     only.
>     
>     Improve PostgreSQL internal shutdown sequence by issueing FAST then IMMEDIATE
>     the KILL ABRT. (IMMEDIATE wasn't used previously)
> 
> 
> Diffs
> -----
> 
>   server/src/storage/dbconfigpostgresql.h c4c5f19ef8e3f57018e8a7e921a726dc9e5b17dc 
>   server/src/storage/dbconfigpostgresql.cpp 3ca098bff11e3e9824c7b555fe96039329c1fbcf 
> 
> Diff: https://git.reviewboard.kde.org/r/113909/diff/
> 
> 
> Testing
> -------
> 
> no(t yet) :-) (well, it builds)
> 
> Is there a 'make test' or similar I can use for that ?
> 
> 
> Thanks,
> 
> Cédric  Villemain
> 
>

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list