Shared system resources - Mailing list pgsql-general

From oleg yusim
Subject Shared system resources
Date
Msg-id CAKd4e_GNsLAArBPS9eihBzDD=0+xEgE_ArinnXLaqWJLmkkWrQ@mail.gmail.com
Whole thread Raw
Responses Re: Shared system resources  (David Wilson <dw+pg@hmmz.org>)
Re: Shared system resources  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Greetings,

I'm looking at the following security control right now:

The DBMS must prevent unauthorized and unintended information transfer via shared system resources.

The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.

From previous discussions, I understood that session in PostgreSQL is closely associated with process, and it is essentially new process for every user connection. In regards to that, my question would be:

When user disconnects, process is terminated and all resources are released, does memory, session/process stored information at gets "sanitized" or just released as is?

Thanks,

Oleg

pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: Table with seemingly duplicated primary key values
Next
From: David Wilson
Date:
Subject: Re: Shared system resources