RefCell<T> already borrowed about rust-postgres HOT 4 CLOSED

My gut feeling is that it's the same root cause as #31: rust-lang/rust#13246.

from rust-postgres.

Your gut feeling is correct. My code is equivalent to the following

extern crate postgres;
fn main() {
  let pool = postgres::pool::PostgresConnectionPool::new("postgres://localhost/postgres", postgres::NoSsl, 1).unwrap();
  let _ : Vec<i32> = {
    let conn = pool.clone().get_connection();
    let stmt = conn.prepare("SELECT 1 UNION SELECT 2").unwrap();
    let rows = stmt.query([]).unwrap();
    rows.map(|r| {
      r[1]
    }).collect()
  };
}

which currently will drop the PostgresStatement then the PooledPostgresConnection and then incorrectly the PostgresRows. This means that the access to the connection while dropping the rows will race with anyone using the released connection. Ouch.

from rust-postgres.

You can work around it by splitting the last statement to

let v = rows.map(|r| r[1]).collect();
v

I might redo the internals a bit to store an Rc of the thing they have a borrowed pointer to to force the destructors to run in the correct order until the underlying issue is fixed.

from rust-postgres.

I believe this should be fixed by rust-lang/rust#21972.

from rust-postgres.