On 2019-06-06 23:51:02 +, Jan Bilek wrote:
> Process For Managing Secure Data With PostgreSQL
[...]
> Another process running with permissions to access the underlying data is then
> running (probably running as postgres user):
>
> 1. Run the following forever:
>
> a. Wait for pending_s
Thank you all - Karsten, Benjamin, Pavel, PostgreSql team,
I've discussed all your inputs with our developers and they came with a
solution for this problem, which was already agreed (on a high level) by our
auditor.
I am adding it here so it can inspire the others, when potentially getting in
On Thu, Jun 06, 2019 at 11:41:40AM +0700, Benjamin Scherrey wrote:
> You should never store such information
> in a database product unless you plan of decommissioning ALL of the media
> that stores the information once you're supposed to lose custody.
Use a tablespace on a dedicated disk.
Move
Postgres has spent several decades creating a data store that does its best
to make sure data is accessible and never accidentally lost. The cobc8of a
secure forensic wipe is anathama to the product goals. To have any hope of
implementing such a thing with confidence you'd need to drop most of thos
Hi
čt 6. 6. 2019 v 1:23 odesílatel Jan Bilek napsal:
> Hi team,
>
> anyone? Please let me know if this is not a correct group to ask, I'll
> move it somewhere else.
>
this question, proposal is much more related to pgsql-hackers forum.
Currently Postgres doesn't support any feature like this.
Hi team,
anyone? Please let me know if this is not a correct group to ask, I'll move it
somewhere else.
Thank you in advance & Kind Regards,
Jan
On 2019-06-04 08:56:47+10:00 Jan Bilek wrote:
Hi,
We've build a Payments Authorisation system (Box solution) on Postgresql
database and now we are
