#417 Prosody broken after each PostgreSQL restart

Reporter aef@raxys.net
Owner MattJ
Created
Updated
Stars ★ (1)
Tags
  • Priority-Medium
  • Status-Fixed
  • Milestone-0.10
  • Type-Defect
  1. aef@raxys.net on

    *What steps will reproduce the problem?* 1. Use PostgreSQL as backend for Prosody 2. Restart PostgreSQL while Prosody is running *What is the expected output? What do you see instead?* I would expect that Prosody keeps working and reconnects to the DBMS. It does however not accept any new connections afterwards and messages are not delivered between users anymore. Basically you have to restart Prosody make it in any way usable again. *What version of the product are you using? On what operating system?* Prosody 0.9.4-1~wheezy1 on Debian GNU/Linux 7 "Wheezy" Note: I only tested it with a PostgreSQL connection through UNIX domain socket without password authentication, which is the preferred way to use PostgreSQL on a local system.

  2. MattJ on

    Hi, sorry for the delay in processing this report. We've been working on improving the SQL storage module a lot in 0.10, and will have a beta out "soon". I'm setting a milestone so we don't forget about this report.

    Changes
    • tags Milestone-0.10 Status-Accepted
    • owner MattJ
  3. Zash on

    mod_storage_sql2 it 0.10 should reconnect if the connection goes away now. Also see #416 and #268

    Changes
    • tag Status-Fixed
  4. Zash on

    mod_storage_sql2 has now replaced mod_storage_sql and taken its name.

New comment

Not published. Used for spam prevention and optional update notifications.