Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1prxrN-0004Zv-Ny for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2023 09:24:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1prxrM-0002Ui-EW for pgsql-general@arkaria.postgresql.org; Thu, 27 Apr 2023 09:24:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1prxrM-0002UZ-3k for pgsql-general@lists.postgresql.org; Thu, 27 Apr 2023 09:24:16 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1prxrJ-005Lhr-G3 for pgsql-general@lists.postgresql.org; Thu, 27 Apr 2023 09:24:15 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-95369921f8eso1335088166b.0 for ; Thu, 27 Apr 2023 02:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20221208.gappssmtp.com; s=20221208; t=1682587453; x=1685179453; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=oLx5gilXSKgeAj0MjfP4FZXI1t+RZaBX2YbyaZ5/in4=; b=uo0gbzIVpY+Uc1iT75IJRKzO7AgOin9m4aHCScEtAolIUBvfhiQ9aYKK49AJImF6QF 3NrFklcraYTUD6WQXSSuAbv8/EZv3QFg5u9So05zygGW0lrj/1+2P6IuXa5EaS6g//ty Fy3LkIbi8kkT+08ZTOleB2mjb9nCh1olLIVpi6C7RrDVTESAB9wmeGI07yzbDOQPWRLq gAn9oglK0N+nbQbNU9CtaeqamOdNz0HgZQ3MlWSlor+4WfmtbwRISqRyO85rp8as03Nx 0Qmfy9VopE61IsRajLnAQHWqF+RytDtvmSOVwAeFavW1L9/TfydYfu76DkcyopWemBR6 0fng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682587453; x=1685179453; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=oLx5gilXSKgeAj0MjfP4FZXI1t+RZaBX2YbyaZ5/in4=; b=FusB1SNhi1j3NupbMxKppngjM6oB95qdKxwTQUxxXeUmIwGaijUmqyWZGNJS/29Xsf JQhGP8D+kdzKEK6/pNRjEr7hf6N1K3mpMI4i4w+U4r2rjbsbosSwoVTG4bHOLzyloWqG rmJ1jcuDLzLg9WM2YLcCxhB87E/cI5DBGM9uNZDdH1Scsm4GNIWVXuMTloi4uj2qYjdc Cx9aaH+KdtFCNNSVFKicfHkf9wvtdHWQSXqeI5RVcLgzix3h4GY48buSqZqjcBKLbYm6 Wd8IxTt8g3CbZVlfw3t1ZPt8/dipT9sJFHvRJ0/jIequzukzLJ5IXC3QPB/A8Y/z3Fzd B2CA== X-Gm-Message-State: AC+VfDznLJYJs2yNh9Qxz+8GXhZbDO4y0P7Zf1uEh1jY1D2m8OnPb3QP VRFs7zc/i2Bri8O+JNIxZttS11eYq9zm6R8q/DWu3w== X-Google-Smtp-Source: ACHHUZ7W+HL6VR07YLwz4UlM/zno15a26SMORsC/p62PpALM+AiuWlRIeJkfYtti+wRN0uiELoUBBg== X-Received: by 2002:a17:907:94c2:b0:94f:956:b3f7 with SMTP id dn2-20020a17090794c200b0094f0956b3f7mr1116619ejc.2.1682587452710; Thu, 27 Apr 2023 02:24:12 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:387b:5a4:e99:4794:568d]) by smtp.gmail.com with ESMTPSA id a11-20020a17090682cb00b0094f5179540fsm9256163ejy.83.2023.04.27.02.24.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 27 Apr 2023 02:24:12 -0700 (PDT) Message-ID: Subject: Re: PostgreSQL in-transit compression for a client connection From: Laurenz Albe To: Tushar Takate , pgsql-general@lists.postgresql.org Date: Thu, 27 Apr 2023 11:24:11 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-04-27 at 14:48 +0530, Tushar Takate wrote: > Does PostgreSQL support in-transit compression for a client connection? No, not any more. There used to be compression via SSL, but that was removed for security reasons, and because most binary distributions of OpenSSL didn't support it anyway. Yours, Laurenz Albe