On Wed, Mar 16, 2011 at 11:19:38AM -0700, aaronenabs wrote:
> I would like to ask how do i work around this, Basically from my research i
> have found out that PostgreSQL does not securely delete data from its
> tables, rows, columns or database. Instead it is deleted from the user
> interface and kept hidden from the user till it is overwritten by bigger
> bytes of data.
> What i would like to achieve or do is to delete data and locate it using the
> source code or any other means as when data is deleted it still remains in
> parts of the DBMS.
Yes, old versions of modified data still exist on disk, until vacuum reclaims
the pages and they're re-used for new data. PostgreSQL won't let you get to
that data once a newer version is committed, so in order to see it you'll need
to modify postgres, or write your own program to find it.
It's interesting you should describe this as "securely delet[ing]" the data.
If someone can get at the old versions of data, they have access to your data
files, and you've probably got bigger security problems than someone finding
Joshua Tolley / eggyknap
End Point Corporation
In response to
pgsql-novice by date
|Next:||From: aaronenabs||Date: 2011-03-17 21:27:50|
|Subject: Re: Accessing dead rows within postgresql|
|Previous:||From: siva kiran balijepalli||Date: 2011-03-17 05:05:34|
|Subject: FETCH in postgresql 8.4|