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 1lyPlO-0006s7-5q for pgsql-docs@arkaria.postgresql.org; Wed, 30 Jun 2021 02:15:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lyPlM-0001u7-Gi for pgsql-docs@arkaria.postgresql.org; Wed, 30 Jun 2021 02:15:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lyPlM-0001tz-88 for pgsql-docs@lists.postgresql.org; Wed, 30 Jun 2021 02:15:40 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lyPlJ-0003ZF-95 for pgsql-docs@lists.postgresql.org; Wed, 30 Jun 2021 02:15:39 +0000 Received: by mail-pf1-x435.google.com with SMTP id c5so997144pfv.8 for ; Tue, 29 Jun 2021 19:15:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2oizpta/Nl7hoXr9L0m+sh3WHMyRdevKdVFOTsCZdbc=; b=rMJVNUDRN4oGCKO0ruwM0LdxWYF5F/ZxjGWJoKcOji4+OybfUWZIoTXMXX6kNZseoJ 79VEViOGIVI0CuppOpR+2/XuRuEJZWCyCjm1y8VsEXVaYzr3gjBLPs8eOoOlwbm55gmu ZL0I2nMbJWT0Yb1Aalbta36F2k5szJf+d2FsPO8llgrOcOBNC+vBx0tYbP8mfkL+yioR JusahsCmviq+kc1VSKLwWN9w0b9dPRyGWzsY5r2Y/nUof1TQwWRRJ26U9RK0931oZ6vW xJ1S6z4X0h1AV7AuJH5Yrxt7TNDtCQ//AAXyk+Ig2xNH9C7bUoW1Hltzru6mlJZ3a4lT OsHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2oizpta/Nl7hoXr9L0m+sh3WHMyRdevKdVFOTsCZdbc=; b=sw08up8wcjGrtA4UXrh0TdeR86vMiiDsrxAMBGcj31wTOLkzPkhUM4VHIAXjiQ4CmJ o/I+LIAbrrJZIhYhGIeFdwZHqFlsrkUgJdXWAQwZfepZyGgQj+414pR20K74VnSPpk3i ZDKbPBwhVckyK1vFi9aw0rU1Dzcp9w6Ipc4Rlg4UeA6YZcmDEbxrtpKsOycYzbl6hPKf BE9BoCqSkSW/iybhDTS9e1qx8WmQdJHl1D2Ke7XjVmhNmNyc5I4tJyCSGrVQTSBR08a9 cU5f6+xojDewooaqDKISEuPY7JTCyCC+jy2+UIzhlmq+oDIJ97/ru58s05iW5WHTMytt B+TQ== X-Gm-Message-State: AOAM530ajdukL285CwcLwBWjvryerR23vsbT6XBbrtbNCuuW2l/7HeT7 Bs22AoG7V1MFpVTkhihsJ5osR8wzSYCENSv99ECFpg== X-Google-Smtp-Source: ABdhPJxxSSUoPJ4njAYcEtn12+zGK3vHz4veSYGjOl4WH1+IxIaejxgwhgvOq9owPZX0n55K9FtjUIao7g0T/PbUtZI= X-Received: by 2002:a63:5912:: with SMTP id n18mr3703219pgb.108.1625019335876; Tue, 29 Jun 2021 19:15:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Craig Ringer Date: Wed, 30 Jun 2021 10:15:25 +0800 Message-ID: Subject: Re: doc: Document how to run regression tests with custom server settings To: "tanghy.fnst@fujitsu.com" Cc: "pgsql-docs@lists.postgresql.org" , "peter@eisentraut.org" Content-Type: multipart/alternative; boundary="00000000000044bebf05c5f24c34" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000044bebf05c5f24c34 Content-Type: text/plain; charset="UTF-8" On Mon, 21 Jun 2021 at 15:43, tanghy.fnst@fujitsu.com < tanghy.fnst@fujitsu.com> wrote: > Hi > > I was doing regression testing according to the PG-doc at [1]. > The modification at 854434c5 seems not correct, could you please take a > check at it? > > >make check PGOPTIONS="-c log_checkpoints=on -c work_mem=50MB" > > The above command reported an error like this: > failed: FATAL: parameter "log_checkpoints" cannot be changed now > > IMHO, as a sighup GUC, log_checkpoints can't be set in PGOPTIONS, is that > correct? > > >make check EXTRA_REGRESS_OPTS="--temp-config=test_postgresql.conf" > > pg_regress: could not open "test_postgresql.conf" to read extra config: No > such file or directory > > I fixed above problem using command like this: > make check EXTRA_REGRESS_OPTS="--temp-config=$(pwd)/test_postgresql.conf" > > Maybe we can change doc description to tell user he/she should specify the > location of " test_postgresql.conf", thoughts? > > [1] https://www.postgresql.org/docs/devel/regress-run.html Yes, that'd make a lot of sense. PGOPTIONS is more suited for client settings. Willing to cook up a quick patch? -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services --00000000000044bebf05c5f24c34 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, 21 Jun 2021 at 15:43, tanghy.fnst@fujitsu.com <tanghy.fnst@fujitsu.com> wrote:
<= /div>
Hi

I was doing regression testing according to the PG-doc at [1].
The modification at 854434c5 seems not correct, could you please take a che= ck at it?

>make check PGOPTIONS=3D"-c log_checkpoints=3Don -c work_mem=3D50MB= "

The above command reported an error like this:
failed: FATAL:=C2=A0 parameter "log_checkpoints" cannot be change= d now

IMHO, as a sighup GUC, log_checkpoints can't be set in PGOPTIONS, is th= at correct?

>make check EXTRA_REGRESS_OPTS=3D"--temp-config=3Dtest_postgresql.c= onf"

pg_regress: could not open "test_postgresql.conf" to read extra c= onfig: No such file or directory

I fixed above problem using command like this:
make check EXTRA_REGRESS_OPTS=3D"--temp-config=3D$(pwd)/test_postgresq= l.conf"

Maybe we can change doc description to tell user he/she should specify the = location of " test_postgresql.conf", thoughts?

[1] https://www.postgresql.org/docs/devel/reg= ress-run.html

Yes, that'd make a lo= t of sense.

PGOPTIONS is more suited for client se= ttings.

Willing to cook up a quick patch?

--
<= div>=C2=A0Craig Ringer =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 http:/= /www.2ndQuadrant.com/
=C2=A0PostgreSQL Development, 24x7 = Support, Remote DBA, Training & Services
<= /div> --00000000000044bebf05c5f24c34--