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 1q9NBd-000566-G1 for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jun 2023 09:53:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q9NBc-00065z-87 for pgsql-hackers@arkaria.postgresql.org; Wed, 14 Jun 2023 09:53:08 +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 1q9NBb-00065c-Uf for pgsql-hackers@lists.postgresql.org; Wed, 14 Jun 2023 09:53:07 +0000 Received: from mail-yb1-xb2c.google.com ([2607:f8b0:4864:20::b2c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q9NBZ-002J5r-EQ for pgsql-hackers@lists.postgresql.org; Wed, 14 Jun 2023 09:53:07 +0000 Received: by mail-yb1-xb2c.google.com with SMTP id 3f1490d57ef6-bd790f26791so432707276.1 for ; Wed, 14 Jun 2023 02:53:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686736384; x=1689328384; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=n/J4yq5lUQ1U+hdq5lmca18SJLUcCVdKvL5dh1dMpj0=; b=PA8UBs0Mvkt4ybH3aBZU9gyQQSeBsyl67fWZYlPbAwje+sHRs6W4EtKYXKunY0xWoP w/1EAIyqsVCISrSWYeRrBNYeOVYdIQhMnNlma8uU6Z+GG+UFc2oplLygOKUsmwy+ARTY s1wpHqb0YwbULeqmwO04wNar3ix0mcJHolS7ep/vwUES8b8sigfUD0vtC11tEbNym8Fd 6aNO/ZIvuvSK6iZG7smulrea3b3UCd7Fm4Pix15Pc3McbrxZJk6IoAhDgxBgpxYJQeXx BQ0+KLeh2RwidngfVmOC203jxG51r4/BCXk/rU0FCQMT79U3ScL/uzlj8MNhfTsVAccn px7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686736384; x=1689328384; 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=n/J4yq5lUQ1U+hdq5lmca18SJLUcCVdKvL5dh1dMpj0=; b=HyEUY5Idfoj7YesL33n+FC23637jtaHDKmb0O1HV/KDgEm7b7oVPeXXURW0H1Py64h Czit9TqqIgMkLw+AEN2E9z7Etk+UJPwBpP7jj8qIUlldnxFDrL3EchnFXIK266zy0Mni fxdyBRHdjooWp+JdK0niNde4KCWNLn5TG1YwiLJ2FRMuNL2V7KQ2ROxSm0LjyJCfl6Ke ix3Gr19SbpvuqGAw/7P+zzfR6FJJkneJUgwuntmzSa79Ko27BK1gPpJySHqTtP8CVPD7 ejz+v5lBQpTHhaMOYM4+puYOCLtC9Bl6cCU5ZyQ9dbVYY5HcLvKn/ADssVRqztiNnaU3 ARdw== X-Gm-Message-State: AC+VfDyBV4Et85e7OxsV83JqMDNxGPj0ckn3FRAtlMnKGACwTEvQL8SI CX80O3FY7dDv0xdGAbgRWoymaB3JnAjJ71C/MdE= X-Google-Smtp-Source: ACHHUZ7etx7Ul6RXi3HWSk48XfL3+QVtWZCsIeAiRS/U641RHIngk2CevdWZ726ewgY+a8zaaj/a99TiJOvUwdTwg/A= X-Received: by 2002:a25:fc13:0:b0:bc6:1cac:a47 with SMTP id v19-20020a25fc13000000b00bc61cac0a47mr1354412ybd.50.1686736384046; Wed, 14 Jun 2023 02:53:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Richard Guo Date: Wed, 14 Jun 2023 17:52:53 +0800 Message-ID: Subject: Re: Replace (GUC_UNIT_MEMORY | GUC_UNIT_TIME) with GUC_UNIT in guc.c To: Michael Paquier Cc: Masahiko Sawada , Japin Li , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="000000000000003de205fe13eb5c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000003de205fe13eb5c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 14, 2023 at 3:47=E2=80=AFPM Michael Paquier wrote: > On Wed, Jun 14, 2023 at 03:38:10PM +0800, Richard Guo wrote: > > +1. BTW, it seems that GUC_UNIT_TIME is not used anywhere except in > > GUC_UNIT. I was wondering if we can retire it, but maybe we'd better > > not. It still indicates that we need to use time units table. > > Some out-of-core code declaring custom GUCs could rely on that, so > it is better not to remove it. I see. Thanks for pointing that out. Thanks Richard --000000000000003de205fe13eb5c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Jun 14, 2023 at 3:47=E2=80=AFPM M= ichael Paquier <michael@paquier.x= yz> wrote: