holland-coredev team mailing list archive

[Andrew Garner <1236618@xxxxxxxxxxxxxxxxxx>]

Fix pushed to feature branch for inclusion in v1.0.12:
https://github.com/holland-
backup/holland/tree/feature/lp_1236618_pgdump_close_connection

This both sets the connection in autocommit mode to avoid holding long-
running transactions and also closes the connection prior to starting
the backup.

** Changed in: holland-backup
       Status: New => Fix Committed

** Changed in: holland-backup
   Importance: Undecided => Critical

** Changed in: holland-backup
     Assignee: (unassigned) => Andrew Garner (muzazzi)

** Changed in: holland-backup
    Milestone: None => 1.0.12

-- 
You received this bug notification because you are a member of Holland
Build, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/1236618

Title:
  holland-pgdump does not close connection

Status in Holland Backup Framework:
  Fix Committed

Bug description:
  holland-pgdump leaves its connection open, and worse, does so in an
  open, idle connection.

  -[ RECORD 3 ]----+---------------------------------------------------------
  datid            | 1
  datname          | template1
  pid              | 12225
  usesysid         | 10
  usename          | postgres
  application_name |
  client_addr      |
  client_hostname  |
  client_port      | -1
  backend_start    | 2013-10-07 18:24:40.620152-04
  xact_start       | 2013-10-07 18:24:40.623424-04
  query_start      | 2013-10-07 18:24:40.626206-04
  state_change     | 2013-10-07 18:24:40.627177-04
  waiting          | f
  state            | idle in transaction
  query            | SELECT pg_database_size('postgres')

  
  This is done to estimate the backup size, and the transaction should be closed immediately (or at least set in autocommit mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/holland-backup/+bug/1236618/+subscriptions