Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rmeeR-0095VH-3b for pgsql-general@arkaria.postgresql.org; Tue, 19 Mar 2024 18:57:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rmeeP-000291-FG for pgsql-general@arkaria.postgresql.org; Tue, 19 Mar 2024 18:57:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rmedT-00HWUI-EQ for pgsql-general@lists.postgresql.org; Tue, 19 Mar 2024 18:56:31 +0000 Received: from [2a00:1450:4864:20::42e] (helo=mail-wr1-x42e.google.com) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rme5Q-005MXn-PJ for pgsql-general@lists.postgresql.org; Tue, 19 Mar 2024 18:21:53 +0000 Received: by mail-wr1-x42e.google.com with SMTP id ffacd0b85a97d-33e570ef661so2767578f8f.1 for ; Tue, 19 Mar 2024 11:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=percona.com; s=google; t=1710872428; x=1711477228; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=aO/Ypqoyv/fR8BEKvzyzVnBQXHKOKW9MO1kL+Nmg0NM=; b=GcpUY7QKH6feFXXqa/N3pb7r7iKhNlwvMJMUqyoGtg7YdiWEgUDY+A4i/l6MMhpqYj 4A6Osb/kFQGto2UjO/4Vj93/L8gELhbgSDzMpwbfFewxpgp4yD0J8S0wb3dZ1K924lX0 54ICNm94RBxxg30amF5K7YZeUXdGU5gSJ+9c0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710872428; x=1711477228; h=content-transfer-encoding:in-reply-to:from:references:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=aO/Ypqoyv/fR8BEKvzyzVnBQXHKOKW9MO1kL+Nmg0NM=; b=ClmfaYD+ycfsfkpMPQIbVpWaEcsfPC7FXdnFPtjDNadqxGSk8sfpjXvVGpY3g4k8F7 6nO8Ea8E+lG3fMcSV2y6YbL0pGYnX2//pJLvm6x9YXgdoLpCdgChIABEaL7ai5lrJv0K o5uCM3KWUx9srF6H3zy98qc6idOdBsw2S+yfYlZ+/bujb8gH7NAuYv1N7O7TVpL42JTn V8sRZpjNy7YgtZ+lnjQNjASpF8dP8OoRrdJy6Wdiz8LxCEioMrkY3UkpjYHlCUL70HMT Q7DEXF2V9WRLz8wKC4DSoAV1i98h1wocQbZiHB0sYOUjCCBogqYrHbEhrtRLrBIaTU18 476A== X-Forwarded-Encrypted: i=1; AJvYcCUl6YD5r2IhvkkekScVt54HM7AiIe1Snp9dmYLe4B21eVFSVl3VfcfO3B1QAI068zLAGgKyrneWBKLsPU9bQVuhnEH9Nhmm6BLvpAcUeKJCFxEn X-Gm-Message-State: AOJu0YwXbFADUtfpMm5YZU4VkD45qyvSIM/s5AzeSBtj975QnZYjmmLz YAggk6OatGcGn6twO37funHmUESzsXfMiL/+CyBRorbVj96WV138Af4Mth8D5i5mbaaZbcyTxGE lyFg94TiSlpclrXWzsXudi9pByWTEpOiNlN86WstZSZPuruVkLUu7s0P35TntYDGqTCmMq4RQcA YR8Lff/VcIbKyiD2uIUwkb0oPCvtpMKG9OzdG7IQTTLXTv3KmKpsFSGXKXwuyfRpTdbFkHSlGMM tjUGBgphqrZ X-Google-Smtp-Source: AGHT+IH6TyD9gH3kn9PIA8B1IYYa8h7nFNxws6unJ/482qMKsGntAwGIr0zI5h0L9xxCH5baPwH0pw== X-Received: by 2002:a05:6000:184b:b0:33f:8e6d:ab75 with SMTP id c11-20020a056000184b00b0033f8e6dab75mr10661231wri.59.1710872428254; Tue, 19 Mar 2024 11:20:28 -0700 (PDT) Received: from [192.168.42.106] (p4feef0e4.dip0.t-ipconnect.de. [79.238.240.228]) by smtp.gmail.com with ESMTPSA id v6-20020a5d59c6000000b0033ea499c645sm2436842wry.4.2024.03.19.11.20.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Mar 2024 11:20:28 -0700 (PDT) Message-ID: <3adaed22-5e25-4c12-964b-65e70b0c9217@percona.com> Date: Tue, 19 Mar 2024 19:20:26 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Postgres database encryption To: Johnathan Tiamoh , "pgsql-generallists.postgresql.org" References: From: Kai Wagner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CLOUD-SEC-AV-Sent: true X-CLOUD-SEC-AV-Info: percona,google_mail,monitor X-Gm-Spam: 0 X-Gm-Phishy: 0 X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::42e (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hey, On 19/03/2024 14:22, Johnathan Tiamoh wrote: > Hello, > > > Good morning. Please I wish to find out the best way of encrypting a > Postgres database. > > This could either be encrypting a whole database ( I don’t if this is > possible), a specific table and a specific tablespace. There is no default incore mechanism to do that. Depending on your treat vector, OS-Level could be fine or you need to go with any of the incore rebuilds available by some vendors. We're currently working on another mechanism, which enables you to encrypt on a table level. Of course, completely open source project, available on GitHub https://github.com/Percona-Lab/pg_tde Would be happy, if you can give it a shot, and share your thoughts and feedback. > > > King regards > Johnathan T. -- Kai Wagner Sr. Engineering Manager, Percona e: kai.wagner@percona.com w: www.percona.com Databases Run Better with Percona.