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.96) (envelope-from ) id 1wJnna-000JgY-1X for pgsql-novice@arkaria.postgresql.org; Mon, 04 May 2026 07:33:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wJnnY-0066C6-0n for pgsql-novice@arkaria.postgresql.org; Mon, 04 May 2026 07:33:00 +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.96) (envelope-from ) id 1wJnnX-0066By-32 for pgsql-novice@lists.postgresql.org; Mon, 04 May 2026 07:32:59 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wJnnV-00000000PmS-1pBn for pgsql-novice@lists.postgresql.org; Mon, 04 May 2026 07:32:59 +0000 Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-4891e86fabeso46648655e9.1 for ; Mon, 04 May 2026 00:32:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1777879974; x=1778484774; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=ucst0lUrbdfaCXkY3Yx5uBmeNuZB/lM4e/jpoAMTZas=; b=hcu4G4/TmoLNPsg5VanivtDueHEcWDemMrZUvO4I+ls9Y4H5ZeMC8Q3oHzk5McfMp3 qybTrTRQ7oW2vYH0DG1i/ioxZT7gh7k7Tk3tEQiKCb8ZCiTJa86SJE1GBbYpIQd7jaKy pFCcf7hlBO6kaVYLA6lBZ4Yy5uikDGtJJPLAb8/2duvi/8VkDZIISV+JQmzyDc3a7RM2 cFxqvgrveU5rdGwt7ihmExFcP+7Fz76BVaR7yUECB3xK78XnTOSHbW1BBOK0lwvgBfDE xBFx1/Mx/GgUTnKuWs0DI9HZTMZcL76lbLSGpor55R3YjBPgyxEKV67vTv99ZeGsBdd1 CYBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777879974; x=1778484774; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ucst0lUrbdfaCXkY3Yx5uBmeNuZB/lM4e/jpoAMTZas=; b=bD5EydINw8BdeV51GMl5f49YrSZZaQwCrSw/Qxv/8tbOo1QB+6q7/cnjm7ypQ+wZyM 0+TvBgevs+vxL8PKn59cgjOE6LIaCCk0QpdpTcasKct2huq8/uHQSBADCdEJt8dxY7ki vAFJJxi4vBFuBvd6aJvpc0vq0qu71AFozo9xxn7D/He/l6ie0fz3JVFYTTGlNUXmC4Se qdm/Lo4JzbiqX/4Rwm756By8rhmDif0POSn322aEqVDVew8rTPlweMgYfECUCmy2QIRd ov74mmm8VeRIfkT4qhLsREeMeiV6r6mPmoOYVwJcoAzSouLCIkyUSQL2L2o/pvWxEn7w t37A== X-Gm-Message-State: AOJu0YzOiI8XIQfge19xcYr05XhyA7tPBT3tnpzOmJNonTzTh7VQzPB7 ihQqFXv+/00DLGKPfDrzjVvBIx/+1MmoQgj72kOTqe9I0vIQyxET8oobZfECOAOXQFk= X-Gm-Gg: AeBDiesa1XHCI65LNLKp7yjepA4Dr0uPYFj9XP7ocVx3rTlUzw1RtTNzBWrIw5Vw3m9 o1yXpO9t1jLv9zyLPjZ7yzDphpWKoMr1FmvOkb/L9Vzq+jmtsxNJJ9XE+6HnT94Rx0zUWFo8btR 2RsrPl0Wo0YCEYFxY+BWkWM4CMnecNu/Ej7/+xckoSH6wUuw5R/DPGLnIk0cVwpUWWl2R4PmtAe dXcpNT3q4lZsrjG/ZYL2f29Al64pyD2Si8ak4MNW+jwwSAYiLK4jQ2shIZPH5GVtCIgmDjXyAXi DeFq1wEqJVpknQgOcEkHCsiVX6MGZEFP/V5rYL5uzVVHLBwXxA/MTQgSatgb5HPb7wnIzDSb+QG qagRX37aISnfBE3ArSjStm34c///DYMKuYHOhwANN0TxMqw4CjmbRGX/dNcU/sCo5jKIwG0prNv gQ7akpGLur9ak9LS9SVf58+iw4khkvbO8J8gBCL+wOcWGoj/RG4neEsHky1gC5AD4= X-Received: by 2002:a05:600c:a402:b0:486:fba7:b150 with SMTP id 5b1f17b1804b1-48a9865f7c3mr102482745e9.15.1777879974054; Mon, 04 May 2026 00:32:54 -0700 (PDT) Received: from laurenz.albe-K4N0CV00F97414D ([2001:871:70:b334:1618:65e9:b0dc:32a4]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-48a8fe3cae3sm100676335e9.0.2026.05.04.00.32.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 May 2026 00:32:53 -0700 (PDT) Message-ID: <4fb700b7a1f03d88447b40e830a4797ce026a0dc.camel@cybertec.at> Subject: Re: AW: Trying to understand Tuple Header From: Laurenz Albe To: "Subramanian,Ramachandran" , "David G. Johnston" Cc: "pgsql-novice@lists.postgresql.org" Date: Mon, 04 May 2026 09:32:52 +0200 In-Reply-To: <544e6b78efba44e5b004a12a8460aa12@alte-leipziger.de> References: <0f8e5544ae8a412bb637fcc3d15f8aaa@alte-leipziger.de> <544e6b78efba44e5b004a12a8460aa12@alte-leipziger.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2026-05-04 at 04:04 +0000, Subramanian,Ramachandran wrote: > So the next select to the table cross references the pg_xact file to chec= k if hint bits > need to be updated or not ?=C2=A0 How deep does the next select look into= the pg_xact file ? > For example if I roll back and never touch this table for 30=C2=A0 Minute= s and I come back > and do a second select=E2=80=A6will it look back into 30 mins of history = in pg_xact ? Yes. It has to, to maintain correctness. If nobody ever looks at the row, eventually autovacuum will freeze it. Any= pg_xact segment that only contains transactions older than the oldest unfrozen row = will get reclaimed. Yours, Laurenz Albe