On 13 April 2018 at 18:48, Jonathan Morgan
wrote:
> For a system with information stored in a PostgreSQL 9.5 database, in which
> data stored in a table that is deleted must be securely deleted (like shred
> does to files), and where the system is persistent even though any
> particular table like
After you drop a table, aren't the associated files dropped?
On 04/13/2018 02:29 PM, Ozz Nixon wrote:
There are free utilities that do government leave wipes. The process would be,
drop the table, shrink the old table space then (if linux based), dd fill the
drive, and use wipe, 5x or 8x delet
There are free utilities that do government leave wipes. The process would be,
drop the table, shrink the old table space then (if linux based), dd fill the
drive, and use wipe, 5x or 8x deletion to make sure the drive does not have
readable imprints on the platers.
Now what Jonathan mentions -
> On Apr 13, 2018, at 10:48 AM, Jonathan Morgan
> wrote:
>
> For a system with information stored in a PostgreSQL 9.5 database, in which
> data stored in a table that is deleted must be securely deleted (like shred
> does to files), and where the system is persistent even though any particula
On 04/13/2018 12:48 PM, Jonathan Morgan wrote:
For a system with information stored in a PostgreSQL 9.5 database, in
which data stored in a table that is deleted must be securely deleted
(like shred does to files), and where the system is persistent even though
any particular table likely won
For a system with information stored in a PostgreSQL 9.5 database, in which
data stored in a table that is deleted must be securely deleted (like shred
does to files), and where the system is persistent even though any
particular table likely won't be (so can't just shred the disks at
"completion")
