Re: Data Packaging/Data Unpacking

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Kevin Grittner <kgrittn(at)gmail(dot)com>
Cc: oleg yusim <olegyusim(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Data Packaging/Data Unpacking
Date: 2016-01-13 21:29:34
Message-ID: CAKFQuwZwk9NFptg36Si6gDM=eDZ7V4XxsvPtRjQJtVbt9T0+zA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jan 13, 2016 at 2:19 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:

> On Wed, Jan 13, 2016 at 2:57 PM, oleg yusim <olegyusim(at)gmail(dot)com> wrote:
>
> > Say, I got network package. The package was decrypted by OpenSSL. Where
> this
> > data are, physically, at this moment?
>
> Process-local memory for the PostgreSQL backend process associated
> with the database connection.
>
> > Opposite situation: we are about to send results of SELECT statement over
> > the OpenSSL tunnel. Where are the data, physically, between the moment DB
> > engine returned results for my query and moment the package was
> encrypted by
> > OpenSSL?
>
> Process-local memory for the PostgreSQL backend process associated
> with the database connection.
>

​In other words (?) while OpenSSL may be a separate project the method of
its use involves loading all relevant code into the process space​

​of PostgreSQL - specifically the process that was forked when the SSL
client connection was established.

David J.​

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message oleg yusim 2016-01-13 21:37:47 Re: Data Packaging/Data Unpacking
Previous Message Tom Lane 2016-01-13 21:27:06 Re: WIP: CoC V5