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 1uMP9R-00Am5w-HC for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Jun 2025 10:45:49 +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 1uMP9Q-0020Fu-9Q for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Jun 2025 10:45:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uMP9Q-0020Fj-0J for pgsql-hackers@lists.postgresql.org; Tue, 03 Jun 2025 10:45:48 +0000 Received: from mail-pj1-x1030.google.com ([2607:f8b0:4864:20::1030]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uMP9N-000Fds-2O for pgsql-hackers@lists.postgresql.org; Tue, 03 Jun 2025 10:45:47 +0000 Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-3114c943367so5965659a91.1 for ; Tue, 03 Jun 2025 03:45:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1748947545; x=1749552345; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ZcEt/TioWNG0kCzWogwzLHk/Z0q6dam7AUPdzL43wtA=; b=gOTyKul8J726ThLY4okU4FXQ5IvAARXLTOIuemGMHF2hqAGrybH+yO2fT3NJ62C3yL 9C8cFniO62AVHhOaspnLIF+cq8DZadh9UbNbRgtDwkua+Ns584Wq+V5+sJAJCOKFT67I CF4qddi5yKcqwlnTkzhnVy+u2e3dd5W7ZEdViv4uglon9J6iWvGMju4kGfdXFeQsnihh cghnKTHho5pcq27OmSeIKWARxAeBt2TNmMrRxh2EVM43v2Usr73LcSb1kye0caSViCRm d+rtwtGUMqIzab1n2FuOc9WN9ZufCMtEhxF4F40qkJ0Gxrap63gDZ+wmSB2UiItaRV+4 6VlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1748947545; x=1749552345; h=content-transfer-encoding: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=ZcEt/TioWNG0kCzWogwzLHk/Z0q6dam7AUPdzL43wtA=; b=wpXyiTFk2Oxcw1mzmTYVuVJzwzc/k2uKXms7/LZGE/J9PSVKCw9LwJIsrfug+/JJKU SoOtP08bEDixOK/cWmPJp1kgq6iuQNoosQg3q6OyeUHrqPbDUb9UCfBURJlyiB2rpDRw Wp/9LCj5WwIFPnt7Jp0Zghk7g8Q6qyNxoeo9nV+pQX+ezaerjPbzd7jImv8sde/7ftmK W8Du99bW2UEe2HQ7ESsC0aPaLZ4dxX7Gkuwi2DOPosZtDIejTrW+u92jb938p0m+BK06 uQQSfkaBMIX37Alt3fgbj14KEwxnIRYWSRRDKvnDBBvonRfekjTOHZ2LtKJDcq/EqzFy zsDg== X-Forwarded-Encrypted: i=1; AJvYcCXSkVk4VsHSY8tk1OLlsowdFfftjKIowqMIB2BQFSdW1RHSuSMxep7JwbC8qpKlIRjXuv9OWqm4TpzZn4k3@lists.postgresql.org X-Gm-Message-State: AOJu0YzfmSPVRDK8xpyYEBGFA+a09ayljhWeDSi5eV4HaV04AWNSTW6a 6vPoCmF1bTNnMEn/lvUPnvL1uuqH5bxUTC6DbSZayraNn8xjBoBp9BNvX50QXQ8j9JuaFeJ7CdM fRFUiYw6YMaByX7s8aJt1SylUNwR3GtKc3rIy X-Gm-Gg: ASbGncuyd7rj2YhBYTjFG7yvxz21Qcg4bTlwTpT3OXj041TT8AC0LbFcb6nCumCL8cF 5a6ACf24uZXdnSKC4U5GSqSr8cMvNbOotfwEDz7Jp+YlaFQJcbLLoMQYT1ZzkAab2N/dhRXGiS8 fDtfGbfHPSyhDxQ0dBKmWaA03tTcKg2ECEGvpdux1F+fhAyMDElJzASRmPYPSaRf290PaZhy+mJ w38dw== X-Google-Smtp-Source: AGHT+IH32sc0us534MceAwBTbWkT1KbQBsnCtaqtRRd1pzRky3qclZwsmY81hEY74jHMtfmH34UorfMFivn21L2PX30= X-Received: by 2002:a17:90b:3812:b0:311:b0ec:135b with SMTP id 98e67ed59e1d1-31250427cc9mr24156032a91.24.1748947545426; Tue, 03 Jun 2025 03:45:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Etsuro Fujita Date: Tue, 3 Jun 2025 19:45:34 +0900 X-Gm-Features: AX0GCFuKub0vg6BRc2c-ZdyzOz9j3QjGWXJ7hRLbAV6MULR4_E6gSbYqIkZRGis Message-ID: Subject: Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable To: Michael Paquier Cc: Fujii Masao , Etsuro Fujita , pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jun 2, 2025 at 12:33=E2=80=AFPM Michael Paquier wrote: > On Mon, Jun 02, 2025 at 12:03:50PM +0900, Fujii Masao wrote: > > I'm not sure this change should be considered a bug fix, > > since the current behavior of postgres_fdw with a local read-only > > transaction isn't clearly documented. Some users might see this > > as a behavioral change rather than a fix. Anyway if we go with it, > > shouldn't we document the change in the v18 release notes? > > After going through the thread and the commit, I have to admit that I > was surprised to see this applied on HEAD now that we are in feature > freeze. This is a behavior change. Perhaps this could be done once > v19 happens, still it's rather unclear if the new behavior is better > than the previous one. No, this is a fix, not a feature, as discussed in the thread; as mentioned in the commit message, the previous version of postgres_fdw could cause surprising behaviors that would never happen in normal cases where a read-only and/or deferrable transaction only accesses/modifies data on the local server, so this commit fixes those behaviors. But yes, it makes a behavior change, so I think it=E2=80=99s a good idea to add a note about that to the v18 release notes, as proposed by Fujii-san. Thank you for the comments! Best regards, Etsuro Fujita