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 1n9hx6-00023u-MP for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jan 2022 06:26:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n9hx5-00077e-6m for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Jan 2022 06:26:43 +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 1n9hx4-00077V-TW for pgsql-hackers@lists.postgresql.org; Tue, 18 Jan 2022 06:26:42 +0000 Received: from mail-pj1-x1036.google.com ([2607:f8b0:4864:20::1036]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n9hx2-000337-HJ for pgsql-hackers@lists.postgresql.org; Tue, 18 Jan 2022 06:26:42 +0000 Received: by mail-pj1-x1036.google.com with SMTP id n16-20020a17090a091000b001b46196d572so1862406pjn.5 for ; Mon, 17 Jan 2022 22:26:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=npqcDlUaTPr64bdAFLY/IozltOLEOMLGOLEUmgBdigE=; b=E6cChxwQiKPHXpuNppJ2vHaAFHqTKHyvT8nbWMG05K7PW8sS3fBxwnF8ZtpeiQ7+IC LMw9fL4uc2bMMxkD+YAeA1OwPYib3R6RzPEXSiWB+PhbPA5FLQQrXdH5HAgqqIw2aUre WWBBtEW9y3/xNDXkELh4oMcDE5dVhrQOQRpUnsoy+UsTXze7CXmBFie68j2b+g0oUaow 9USsQKS4gXrtXfnLXNh0cUeZN9QhgDdB5kCQ67kQ0IWF2Yd/JZBB6J3hSRVPvfN+57p+ 5oenBjJ0pGSCMrqd/D/D0P10twVuhA8FyeDTn3vKBKKU80brKZAvB0VRSUXmwz7Pg10E b3KQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=npqcDlUaTPr64bdAFLY/IozltOLEOMLGOLEUmgBdigE=; b=FsACK5wbb8rKJbh/6RlJ8ErYXRp0HhB8VfHMA+42MrVEcBIn5VCBwibOrVrygxoBiC Hi9LpB4Wm3HF1e3k7KggVYsX8m1KnPHh2oqdir0Fda6rPQiOnONalirTiHLbN/vlbDIi oIRwsp4ONN96cNhXhFk4R52sGfvtbYumfPI3I7MC8g+EjfaxSbzPvTkreH5VNeVT7K6S 6bPx6BIQIhaDzAXBXUdJIxLiekyAml81NWHxRlGdyZtP0rnNo0d6Ubf2PNA+fgaJE21Z CX/fQ/8858fEoUjW4XVWJTcYgIGtk2mcCfUvfv01rGq8Fu99wjSi2UTw0YPtdOmIzh+b q4fQ== X-Gm-Message-State: AOAM530i0Ge1shLNPKqifc5z7cw2Icj2jTSPcEwjc6w5qcq3E7QGDxir Z/IR5ZTtFOkKTiZHXmdW5h0= X-Google-Smtp-Source: ABdhPJyFEgL15j2UrZk2Mw1GKe6w68Oo9oHk4UiTwQbDuDhY0b7bP3+2iYINuffPOPKGPUuWbGmJzg== X-Received: by 2002:a17:90b:1292:: with SMTP id fw18mr29311340pjb.36.1642487198539; Mon, 17 Jan 2022 22:26:38 -0800 (PST) Received: from jrouhaud (1-171-184-213.dynamic-ip.hinet.net. [1.171.184.213]) by smtp.gmail.com with ESMTPSA id n14sm13565795pgd.80.2022.01.17.22.26.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Jan 2022 22:26:37 -0800 (PST) Date: Tue, 18 Jan 2022 14:26:31 +0800 From: Julien Rouhaud To: Kyotaro Horiguchi Cc: jakub.wartak@tomtom.com, pgsql-hackers@lists.postgresql.org Subject: Re: In-placre persistance change of a relation Message-ID: <20220118062631.khvzzhwwzw4ykmtm@jrouhaud> References: <20201111.173317.460890039962481381.horikyota.ntt@gmail.com> <20211223.150141.567663666306444193.horikyota.ntt@gmail.com> <164189363522.31345.3832968263786650864.pgcf@coridan.postgresql.org> <20220114.114310.2172685740667639154.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220114.114310.2172685740667639154.horikyota.ntt@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Fri, Jan 14, 2022 at 11:43:10AM +0900, Kyotaro Horiguchi wrote: > I found a bug. > > mdmarkexists() didn't close the tentatively opend fd. This is a silent > leak on Linux and similars and it causes delete failure on Windows. > It was the reason of the CI failure. > > 027_persistence_change.pl uses interactive_psql() that doesn't work on > the Windos VM on the CI. > > In this version the following changes have been made in 0001. > > - Properly close file descriptor in mdmarkexists. > > - Skip some tests when IO::Pty is not available. > It might be better to separate that part. > > Looking again the ALTER TABLE ALL IN TABLESPACE SET LOGGED patch, I > noticed that it doesn't implement OWNED BY part and doesn't have test > and documenttaion (it was PoC). Added all of them to 0002. The cfbot is failing on all OS with this version of the patch. Apparently v16-0002 introduces some usage of "testtablespace" client-side variable that's never defined, e.g. https://api.cirrus-ci.com/v1/artifact/task/4670105480069120/regress_diffs/src/bin/pg_upgrade/tmp_check/regress/regression.diffs: diff -U3 /tmp/cirrus-ci-build/src/test/regress/expected/tablespace.out /tmp/cirrus-ci-build/src/bin/pg_upgrade/tmp_check/regress/results/tablespace.out --- /tmp/cirrus-ci-build/src/test/regress/expected/tablespace.out 2022-01-18 04:26:38.744707547 +0000 +++ /tmp/cirrus-ci-build/src/bin/pg_upgrade/tmp_check/regress/results/tablespace.out 2022-01-18 04:30:37.557078083 +0000 @@ -948,76 +948,71 @@ CREATE SCHEMA testschema; GRANT CREATE ON SCHEMA testschema TO regress_tablespace_user1; CREATE TABLESPACE regress_tablespace LOCATION :'testtablespace'; +ERROR: syntax error at or near ":" +LINE 1: CREATE TABLESPACE regress_tablespace LOCATION :'testtablespa...