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 1s7PLI-005YMa-Nr for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 00:51:34 +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 1s7PLI-00Bnz9-Le for pgsql-hackers@arkaria.postgresql.org; Thu, 16 May 2024 00:51:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s7PLI-00Bnz1-Bs for pgsql-hackers@lists.postgresql.org; Thu, 16 May 2024 00:51:32 +0000 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s7PLE-000SM5-Ri for pgsql-hackers@postgresql.org; Thu, 16 May 2024 00:51:31 +0000 Received: by mail-lj1-x232.google.com with SMTP id 38308e7fff4ca-2e3fa13f018so2027461fa.3 for ; Wed, 15 May 2024 17:51:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715820688; x=1716425488; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zyYfXKRbZ0TLzQr4XNM7ZwGmXVNxClpsLdH5ujv0CyA=; b=jvuttarGHvoBDnLotRMm4T6MKCJ1NwpY8ybJqQFU4ZQUUDgcfATDHiBec0jnZaw77c WkXxlUzRk6a3uzlC5xnMF0/atjq/6aVRVYCPxYsavM1dvJ1Vmpzg40B0UtoHVpg6RmAn d4Nr5AnfQDD4WsnqtE7VbE1pTWMhchWNNT8/W4tNIVRqtJ7XlQJtYb0i5wDIScFZ7HaR z1OfBQcTyMrOtCt7rvR7YZ0D3LpOYSct8PnAirZtgEWP8Zd8dKlvUbdwyPlLeMcTGQWO zhIcUaETXKhEIWEN1DmXXxFEuU8oWwp+dJ2Xr8SMT0+ygL0LF3NgIFUo59IRb2nUyMUI eQSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715820688; x=1716425488; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zyYfXKRbZ0TLzQr4XNM7ZwGmXVNxClpsLdH5ujv0CyA=; b=FPj3Gw0bRnJE8fp4gWJmM2ux/EVtrHyxMsNSa/UUcRPvWvLttAFq/dLeSOEKrnjUJE wvEgvyRcpeeSn/10mS99kzQsDToa2soYAF/3vY3Eet5KyMSnJfAeG2gKtmMQTW8eTuKk 0tP/nkXMLcfGSVFy7aOrSPOCHDLkoGiKYETQFDUXmvn/KRL0soFHQRgpjHgcacJ8el/5 teIdSuo/UtNzNvE0PfX0RVHeV50CBs9+XJTirZWy3KMTSYKKRkWPxn8vbvlyXtJ/1/al TrCzGKkINlaKwqRihDFcL08PAD9+3L/PTQMaEeMUZHsWRw9+XgzF2/LH8ddcKQLQPVi3 tHqw== X-Forwarded-Encrypted: i=1; AJvYcCW33VcuS17o3yaqJDafBL088mP00HIvb0LE9jFhYVjRxkzJgkpBtw1QtfFFS7J8ROmdZRpf8z8+AcxRhawy64y34jxxk1W6nWm8SSwd X-Gm-Message-State: AOJu0YzusvTFc0YRNval8C4ssq+ia7O1CkS3y3bdhYPQSRrdMA4c53Kx Xk4ORWnzAVbqdHEiSOMoZOhwWR0ScwzQoU3hqQU9+tCYtK6oY9SUgu87GA+WikQQGAVY2uifCMC AitqERSn7+yUmNhP6gkFEkbk7GWo= X-Google-Smtp-Source: AGHT+IEYYQH47/tvgMwCOrPTCUAkqNqJVnEW1wCaJeZd0sXMrJ5fAuH3L9pS509olvwgpU78V8WfCino9U0SpQA0Wpo= X-Received: by 2002:a2e:998f:0:b0:2e0:1414:5eb9 with SMTP id 38308e7fff4ca-2e51ff4d5a5mr110667111fa.25.1715820687546; Wed, 15 May 2024 17:51:27 -0700 (PDT) MIME-Version: 1.0 References: <1644622.1715736217@sss.pgh.pa.us> In-Reply-To: <1644622.1715736217@sss.pgh.pa.us> From: David Rowley Date: Thu, 16 May 2024 12:51:15 +1200 Message-ID: Subject: Re: explain format json, unit for serialize and memory are different. To: Tom Lane Cc: Michael Paquier , jian he , Daniel Gustafsson , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 15 May 2024 at 13:23, Tom Lane wrote: > > Michael Paquier writes: > > Perhaps Alvaro and Tom would like to chime in, as committers of > > respectively 5de890e3610d and 06286709ee06? > > No objection here. In a green field I might argue for > round-to-nearest instead of round-up, but it looks like we > have several precedents for round-up, so let's avoid changing > that existing behavior. Thanks. I've pushed the patch now. David