title: Postgres did not free the space to OS after TRUNCATE of a 145GB table
body: <p>I truncated a 145GB table today, but the space did not return to the OS. I already validated inside the database, and the table is now empty. </p>
  
  <p>Despite space was not freed to the OS, I notice that running the <code>du</code> command in the partition already reports 145GB less, but when I run <code>df -h</code> it does not. A discrepancy of 145GB cannot be because of inode size. </p>
  
  <p>I am running a Mirth server with a Postgres 9.3 database in a CentOS 7. </p>
  
  <p>Any clue why space was not freed?</p>