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 1vDUK3-00AFCt-KW for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Oct 2025 21:00:10 +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 1vDUK2-009Ouq-DV for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Oct 2025 21:00:09 +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 1vDUK2-009Ouh-1p for pgsql-hackers@lists.postgresql.org; Mon, 27 Oct 2025 21:00:09 +0000 Received: from mail-io1-xd36.google.com ([2607:f8b0:4864:20::d36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vDUJy-004a5Y-1N for pgsql-hackers@lists.postgresql.org; Mon, 27 Oct 2025 21:00:08 +0000 Received: by mail-io1-xd36.google.com with SMTP id ca18e2360f4ac-92b92e4b078so226434539f.0 for ; Mon, 27 Oct 2025 14:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761598804; x=1762203604; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=8jaAk0OiiC5CuLOr+DLmShr8mFv5kqcUnmm4raVZHmY=; b=bdWwmNIJNZA0SeTKXwp4YpvUleJlYIwyc13OtondzPx5hp3WtMOcBO5Z3Bynu/lr13 5kkXmcOl8kyPBBYuQkgzC4Y8DJaS+7EdZ5fCEJnp+zRQ2z29Mjmppz72zgmIvpT1QDRe DfNJr8qyDJ+uHgSZF0RqwDsjIAlKNn+C+22IxppVuWO6QunshNaFhVDScFMnjOnj6ACz 4uCLlSegnfm119EUzu3hCvYRmFwD2ihfyXYXeFzy0kDoHGhetrpuGMu/g3qbXlKLXUDV SY+HWHLV60bA5piJ6Ab3C6beQriEjM710i74UzuTqpNoFBdQjeetDL/AznHPKot4J7Au 91Zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761598804; x=1762203604; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8jaAk0OiiC5CuLOr+DLmShr8mFv5kqcUnmm4raVZHmY=; b=p4d9C8wrEPNMzeUGb43RGSHU2bfuEZgmZC0sbVNw1dLB+afHOBsGpBgDamGpY0cWSl KhoSxVzBj7RgWHH2Rb2nrDKCljyRfhso01LJSqeWYFLBAhEkjGOAarp4TE2t4d7brEX3 wSErQjZCPgYonRGJxvXmblnkGP8uYeMTvPinUiCv6Xroc5TqANRUasYlBbUxBDUrVqGZ 3v9EneOyRsveN9D7hl+Lrc4ont1sJPGM0XvwhdxwIke7zUOGrlIzz8FuXQu1bFNNd05h Xv8r/1DI/7FD3hF/TooM4PC2cOHNgttQeO9zGITzqEmtmzVIsoIUVZlsUKWFTyhEtgSb j7mg== X-Forwarded-Encrypted: i=1; AJvYcCVUiOGyPkHiIG1GpEunFEhZP1KVhozJOZ/P9FZ+AqE+Qx7nnbrVeUrtF4CWK8nexfgomRxumd3IjUM+HWdT@lists.postgresql.org X-Gm-Message-State: AOJu0YwSrLFfUdwYnS9RLR3ICjWy1ZCpWAGAxJCFcXjwaoHnsd3p/NHD ERV+xBqHiPZARHW04aYe9Pm9KLZ2mbQcx/YMWdnK0jbCBYRMHsuljghM X-Gm-Gg: ASbGnctLcCVSPdVBeFc57RBWK9ic6Qnfy180G/Qfsi0sU3UYypDHP2lZwAHeOxHkqwX X6lKQUZ5v/8cMyt1rzGgb11xphKQsI87XOlVICuNBfbXvuru33tBNxMHS5Ymm1S0xFBUKiyvWTg MDwQLANPAEJk5sS5vikmEQwoNiq3F6BvnL345b/d4cPcXnD0kBvjrCDx1Ou+Ms7SxPH1BC4x086 8YkrIQXwtXCyalIhvWIiI8PSoki1wG0WEK2LtG0mzoUn0a1WOWd+slC4LB/H9Cao9VOLmMgRQMs /XccIXN5Hb0vEgRQBhDpMtSQW2A8n1uocRomSYLMlfrrhxVs1ZLNV3Qx0fKovXQQJrpg8YEEzSW UoeOXfF+flAEE9+vkdpOmBBq2yHUnlxhfS9lm0jeCmJpc6kIcn/oQqKUGrWgBUP51MqkTSSL7NI NGZdgfw5C7dyHWD18xQEWgIOzO8EANXSXbLcnHDKQ8ydd/voSsTw8zUmWQx+p3e3c/OXMGgzvRC eQ2 X-Google-Smtp-Source: AGHT+IGnxOvcMuir+nmmZQ407wXU/HVncIGGv2YCXPQHLyQ7TN8+UiqnczGXfI7YeKJb0Qgt2EtuVA== X-Received: by 2002:a92:cda3:0:b0:430:ae26:7c19 with SMTP id e9e14a558f8ab-4320f6003c7mr22893385ab.0.1761598803901; Mon, 27 Oct 2025 14:00:03 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-5aea946e0b4sm3518635173.31.2025.10.27.14.00.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Oct 2025 14:00:03 -0700 (PDT) Date: Mon, 27 Oct 2025 16:00:01 -0500 From: Nathan Bossart To: Jim Jones Cc: Fujii Masao , Srinath Reddy Sadipiralla , Greg Sabino Mullane , PostgreSQL Hackers Subject: Re: display hot standby state in psql prompt Message-ID: References: <7b2bd420-9687-4dc3-b5a7-51a24646a5f1@uni-muenster.de> <9d45ca06-cd8b-44bc-9647-c7dd5f4595cd@uni-muenster.de> <171b207e-8fb4-44bb-b6a3-9a12c5a9625b@uni-muenster.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <171b207e-8fb4-44bb-b6a3-9a12c5a9625b@uni-muenster.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Oct 27, 2025 at 09:17:03PM +0100, Jim Jones wrote: > On 27/10/2025 17:23, Nathan Bossart wrote: >> This was briefly mentioned upthread, but I'm a little concerned that this >> doesn't respond to commands like SET TRANSACTION READ ONLY. I wonder if we >> should mark transaction_read_only as GUC_REPORT and use that instead. FWIW >> I see that we marked search_path as GUC_REPORT somewhat recently (see >> commit 28a1121). > > You're right, it doesn't. I like the idea, but I'm not sure how to > integrate a transaction-scoped variable into this feature. Would that > mean we also need to change the reset mechanism for GUC_REPORT variables > when the transaction ends? Hm. You're right, that seems to have problems (I'm curious about the use of stmt->is_local in SetPGVariable() for SET TRANSACTION statements). I also see some past discussions in this area [0] [1] [2]. [0] https://postgr.es/m/flat/3a40f835-116d-0f95-aede-d5236337bbf0%402ndquadrant.com [1] https://postgr.es/m/flat/CA%2BTgmoZsHrHeqh5dYpoH%2BWW5EmT-egMGuyrLTsjKz80WajT4tg%40mail.gmail.com [2] https://postgr.es/m/flat/CAFj8pRBFU-WzzQhNrwRHn67N0Ug8a9-0-9BOo69PPtcHiBDQMA%40mail.gmail.com -- nathan