From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Date: Thu, 18 May 2023 16:10:02 -0500
Message-ID: <5038f5c7-35f6-0dc6-129e-341dd6909ea1@gmail.com> (raw)
In-Reply-To: <ZGaRB7EVdzYZ7Mm+@momjian.us>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com>
<ZGZKN0fQORPPNqc5@tamriel.snowman.net>
<08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com>
<f714e518-374a-8d74-1119-9a363857a367@gmail.com>
<1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com>
<ZGaRB7EVdzYZ7Mm+@momjian.us>
On 5/18/23 15:56, Bruce Momjian wrote:
> On Thu, May 18, 2023 at 01:56:48PM -0500, Ron wrote:
>> We need to keep costs down, too.
>>
>> Oracle (I think) does it at the DB level, and so does SQL Server. Upper
>> Management hears us say "sorry, no can do" and wonders what bunch of amateurs
>> are developing PostgreSQL.
> I have found it is hard to protect against the judgment of the ignorant,
> so I usually don't bother.
It's perfectly valid to ask "why can't they do X when our previous vendor
could?"
I, of course, know that it's because WAL records are global. "They" then
quite reasonably ask why the developers haven't fixed that, yet. The answer
(I think) is that "global WAL"is deeply embedded in the product, and would
require a major rewrite; adding new features is a higher priority.
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
In-Reply-To: <5038f5c7-35f6-0dc6-129e-341dd6909ea1@gmail.com>
References: <CACufLfw0y3v1kfz-OVP5OupP_b5sei-x_gfh16Lx=Pgd6jehrQ@mail.gmail.com> <ZGZKN0fQORPPNqc5@tamriel.snowman.net> <08c133e0-b136-ff80-886e-b0d4f621c75c@gmail.com> <f714e518-374a-8d74-1119-9a363857a367@gmail.com> <1d0735cf-b5dd-1c05-d03a-9b52ee2cc5bb@gmail.com> <ZGaRB7EVdzYZ7Mm+@momjian.us> <5038f5c7-35f6-0dc6-129e-341dd6909ea1@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox