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 1u2FVS-00FGmV-KD for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 20:25:14 +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 1u2FVQ-00F45y-Ig for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 20:25:12 +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 1u2FVQ-00F45m-8X for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 20:25:12 +0000 Received: from mail-yw1-x1129.google.com ([2607:f8b0:4864:20::1129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u2FVO-003k8C-2r for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 20:25:11 +0000 Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-7020d8b110aso57935227b3.1 for ; Tue, 08 Apr 2025 13:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744143910; x=1744748710; darn=lists.postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=8vhnGYMuwlkTRZAJnVznd05UDancxKvUkZy5Dz9D86o=; b=RtQglwHdnguLdn4qBDvZ/NSfszg09BazF2stXH0zozvytLFEiCcFVACz1jUfipEqmC jMKxu+C6qJPKDuSA18dQWTnlQwpCx9ge7z/hUPPfy6n66MHa3AvLliLQu9TgppWOUE3a jQ8lUAHwQ8KKMd5oKvCo+JGbuHe5NmkCAiOi+4n8FcGNnyWi7pq86Ich8BfLwrdxl5LC KkFoE690WKM8p8AFGDAcNt6xmhnK+GEoI4waVfdtsSN8TAjOxwYex7i6xJzNoCqW/eKd wKZTi3qa9WHHlrzFG4LBMjErFdIRNOU0Ri6LmLTUUM1Q/MnTS3aigl6KkEzqWtPtWu7I SBSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744143910; x=1744748710; h=in-reply-to:content-transfer-encoding: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=8vhnGYMuwlkTRZAJnVznd05UDancxKvUkZy5Dz9D86o=; b=cbgS3DllKyVeY87WPSm1SZv5GmhMNqElmZDhplgmACY49dUYJZ4toY6PgSZpKm6liW 1MH7M6lL1RM+WqSumW0Lk4iV8kouj+rYYJTRY2rIboLDfwmfJ5Yzh2uYvRX6RfxjptKi nuIDnHTLi4eJlJ3Am9mSwrtt0GDNtHpi/jwF4IzOpFCFbZ3fR6fX7oCLMDa10CDu0iul 9C6ANR2y9iASG+6iOT6eS2nVZRREKCu5CWHP0X2/VESGD5yfPZcmYXYFkimxkliYg0Pk uIPXs4taY2nOQ8k0BG6SWpNcbAo4jDK6EgI+A7JWKN7/TbbJkzbrCmRdbIR1bHkMvIXv i4aA== X-Forwarded-Encrypted: i=1; AJvYcCWaJXbrKUypKxYQkA/MEjYvtCEzOzjakMrbmJ3EuX0IQ9w8hkEaLhMYhoA2geBVT6fjjO3UhdDfWVlVbK8D@lists.postgresql.org X-Gm-Message-State: AOJu0Yx0Exo3eS12/9tOGkTnAX8p9ch4XEgyZfaSFydZRlXuhOTgAT6a LW2M2AD56E+Nk3iHQCFNRV7Kkwf0bWBJVinAA8WNjaN5mbs2hKHp X-Gm-Gg: ASbGncuDeOuHgyu/ZC9C1pwBR/NwCShTv342Iq1ctB5P/RkQj3GOvNHajJN8G+WLDjt 0HH6M4AmpYlYCKTn5u9h4W3Ggd3Zu6nrX48sX+HxJF/qpawNyrNokBHMkhDSgmIPWcDBDqzb/Xd L64IAbfhNoP1mwcNVUHKle8FWHA+ypREZ9SgtYr/PKh3YAWi3b0EgdoiFSb7KhRLcz3yqZVS90B gTfku559PZ2qpa1DwMkvWzr555LnmWBFblPLPpt++y5Ao3AthGpWL67b5jA7edpbcXWW7nThcni LhadXI8zouxATpLxgc9ZFzs2mpwnlV8D8yATCaISCEhFiHMX++JT1LWqO84s0PsuG8mX3p+kP0i SC7uyrLvELY8HP8N7auaZq/+oH3IAghqsrxQ= X-Google-Smtp-Source: AGHT+IGc8diZzqtZqhAo3n3Cg2juhdcuQXoYyRKr2q2QDlFBo0TzCaEUKZnQMUJCKPw4pB+HmpByEg== X-Received: by 2002:a05:690c:88f:b0:6f9:b0a6:6a15 with SMTP id 00721157ae682-705388f7d59mr11714657b3.38.1744143909983; Tue, 08 Apr 2025 13:25:09 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 00721157ae682-703d1f6f3ddsm32512697b3.78.2025.04.08.13.25.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 08 Apr 2025 13:25:09 -0700 (PDT) Date: Tue, 8 Apr 2025 15:25:07 -0500 From: Nathan Bossart To: Amit Kapila Cc: Michael Paquier , Alexander Lakhin , Tom Lane , "Jonathan S. Katz" , PostgreSQL Hackers Subject: Re: Large expressions in indexes can't be stored (non-TOASTable) Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 08, 2025 at 04:44:02PM +0530, Amit Kapila wrote: > On Fri, Apr 4, 2025 at 7:58 PM Nathan Bossart wrote: >> On Fri, Apr 04, 2025 at 05:16:43PM +0530, Amit Kapila wrote: >> > Can we dodge adding this push call if we restrict the length of the >> > origin name to some reasonable limit like 256 or 512 and avoid the >> > need of toast altogether? >> >> We did consider just removing pg_replication_origin's TOAST table earlier >> [0], but we decided against it at that time. Maybe it's worth >> reconsidering... > > I don't see any good reason in that email for not removing the TOAST > table for pg_replication_origin. I would prefer to remove it rather > than add protection related to its access. The only reason I can think of is that folks might have existing replication origins with extremely long names that would cause upgrades to fail. While I think it would be probably be okay to remove the TOAST table and restrict origin names to 512 bytes (like we did for password hashes in commit 8275325), folks routinely complain about NAMEDATALEN, so I think we should be cautious here. -- nathan