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 1oIytj-0002tT-Al for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Aug 2022 20:53:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oIyth-0001hX-44 for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Aug 2022 20:53:49 +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 1oIytg-0001hO-PN for pgsql-hackers@lists.postgresql.org; Tue, 02 Aug 2022 20:53:48 +0000 Received: from mail-pj1-x102b.google.com ([2607:f8b0:4864:20::102b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oIyte-0004QY-4M for pgsql-hackers@lists.postgresql.org; Tue, 02 Aug 2022 20:53:48 +0000 Received: by mail-pj1-x102b.google.com with SMTP id x2-20020a17090ab00200b001f4da5cdc9cso9556345pjq.0 for ; Tue, 02 Aug 2022 13:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timescale.com; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=rFEMqJl6HlFKPxqxILvgID/VjXEjU4DHhbxVMQiX42c=; b=QOlWNia+gkjCniLkdg4iRxcfynD3k4QYgLNhDL9hR4liqjnW125KshOtr7Q7qDwbl6 iKctNCcFO5xVikCqcX+ud+mDtGUT2EG/EMmDp0M8dFQ1bJGYFtjiGYEDChF/dwryU9Sr ISafVgHsF7V1whHcCFXbyJdWCnpzWbsJrpSm1Rfx/2AdvXysRMYdymFr5yPd3lg4l+ZA TNcF+nNWO7l7cmYyPsuKWAQ2iPQgeNUfEWJx6m7aMM2IIVv5C4fKRgrL7nRq1x0tdAmX otSeCVySzLW7N0oYHJMuAb5dKn0eE+AI2xZtcnrS61FSXj7Ndr85xR7eIKIYZ9iJvrvL wz2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=rFEMqJl6HlFKPxqxILvgID/VjXEjU4DHhbxVMQiX42c=; b=4zXS4HR8AXnLLFJM/lcMFl4WtdQuYmg1JhTdLhVcq75uaQGUmbfcUb4mv6K6bZ9dJ9 bhmt0fmJwbY6cAdneKLbelb4DuFeYB1/6whXD5/zupNoX+itFXpo5/w6g2JdXWSNCTW/ DIkWKOALI219P/vAxl6wsmnmfia/fs1259HTroqARDo0i9yhkUZbRDtGGbWtb68dCAL5 uJQ1EkBKrwPONFPo4fcqBKGVkY+iEE8um6v8jPRyylD+xknUcR54H+UhYJMyo5MrKTw2 lchOw/zpjw7+/2ZhJZcqyUMb7jbif2s0k8RrEiSoZNQQSkEyVaEkmcD+cQvgCJ8T4m3t aseQ== X-Gm-Message-State: ACgBeo0Ht1PpjnoypOGkXWW7pfQIwShMvJY8BwIMTetrdL7hIX3sC6wU jhz/61zMwdxTdP99QzZPnIVxVQ== X-Google-Smtp-Source: AA6agR5aihJ7leYP3kqLHNhsqWnstfIifAID3KN7zaICwMN4TDdt6I7YOaveCE1esz6nXVbj+/CKEw== X-Received: by 2002:a17:903:2341:b0:16e:e205:bb3a with SMTP id c1-20020a170903234100b0016ee205bb3amr12967525plh.10.1659473624327; Tue, 02 Aug 2022 13:53:44 -0700 (PDT) Received: from [192.168.1.21] ([50.39.205.221]) by smtp.gmail.com with ESMTPSA id l3-20020a170902f68300b0016d5b7fb02esm141306plg.60.2022.08.02.13.53.43 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Aug 2022 13:53:43 -0700 (PDT) Message-ID: Date: Tue, 2 Aug 2022 13:53:42 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: libpq compression (part 2) Content-Language: en-US To: Daniil Zakhlystov , Justin Pryzby Cc: PostgreSQL Hackers , Andrey Borodin References: <20220112141526.GF14051@telsasoft.com> <20220113235827.GM14051@telsasoft.com> <18CFC392-0391-4439-9F02-FC1CF02FFA24@yandex-team.ru> <20220118043919.GA23027@telsasoft.com> <20220302213352.GA27651@telsasoft.com> From: Jacob Champion In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This entry has been waiting on author input for a while (our current threshold is roughly two weeks), so I've marked it Returned with Feedback. Once you think the patchset is ready for review again, you (or any interested party) can resurrect the patch entry by visiting https://commitfest.postgresql.org/38/3499/ and changing the status to "Needs Review", and then changing the status again to "Move to next CF". (Don't forget the second step; hopefully we will have streamlined this in the near future!) Thanks, --Jacob