Skip to content
Snippets Groups Projects
  1. Nov 12, 2017
  2. Nov 11, 2017
  3. Nov 09, 2017
  4. Jul 10, 2017
  5. Jul 03, 2017
  6. Jul 02, 2017
  7. Jun 28, 2017
  8. Jun 27, 2017
  9. Jun 18, 2017
  10. Jun 06, 2017
  11. Jun 03, 2017
  12. Dec 06, 2016
  13. Nov 07, 2016
  14. Oct 18, 2016
  15. Oct 15, 2016
  16. Oct 13, 2016
  17. Apr 01, 2016
  18. Feb 27, 2016
  19. Feb 25, 2016
    • Stephen R. van den Berg's avatar
      Revert "pgsql: Kludge around clone race in Pike core." · 6f87145f
      Stephen R. van den Berg authored
      This reverts commit f339d7f8.
      
      The kludge should not be needed anymore due to a checked in fix
      in the Pike compiler.
      6f87145f
    • Stephen R. van den Berg's avatar
      pgsql: Kludge around clone race in Pike core. · f339d7f8
      Stephen R. van den Berg authored
      As reported by Jeff Hungerford:
      
      When there is:
      - No connection at present.
      - Two or more threads try to open an initial connection to the database
        simultaneously.
      
      You can trigger this:
      
      Attempting to clone an unfinished program
      /usr/local/pike/8.0.175/lib/modules/Sql.pmod/Sql.pike:342:
          Sql.Sql()->create("localhost:5432","foo","bar","CENSORED",UNDEFINED)
      
      This could be caused by a race in the Pike-core class-cloning code which
      is not racefree when two threads try to instantiate the same object
      at roughly the same instant.
      
      This patch attempts a workaround to detect the race and loop until
      it finishes without problems.  It would be better if this could be
      fixed in the Pike-core.
      f339d7f8
  20. Feb 24, 2016
  21. Feb 18, 2016
Loading