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 1tTHX0-004UoN-Hs for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Jan 2025 09:30:18 +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 1tTHWz-00DNNz-SV for pgsql-hackers@arkaria.postgresql.org; Thu, 02 Jan 2025 09:30:17 +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 1tTHWz-00DNNq-JS for pgsql-hackers@lists.postgresql.org; Thu, 02 Jan 2025 09:30:17 +0000 Received: from mail-yb1-xb2d.google.com ([2607:f8b0:4864:20::b2d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tTHWy-001gtW-0H for pgsql-hackers@postgresql.org; Thu, 02 Jan 2025 09:30:16 +0000 Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e537d9e3d75so14967304276.3 for ; Thu, 02 Jan 2025 01:30:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1735810215; x=1736415015; darn=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=ehheSC50hzplOsi8PH5mCgAYHgHrLSe9FGutXVNdUjk=; b=QNY3VDVf2aQ/hV2v+YODOVghyCKuCMWYDf7iCpvJItfj7Z33mo2fgykPN4pj1qznR0 0K8Dp9VH0lCyhj+XUDJ82p79NO6Iyjg9+f14jkIvRM+XtRTNsiNGt7vD0VygrEZRgNvS 2z5JaDy9V1+rAL1iGm97bSUDaYlAjLGt1okjFnbZk3Jc75yrwq10nGsdJhyhq/X+p5/Z uLlML0IGD55SvdQ8iyS3ZTNtRYR2slN8iV/3zTJO1Y+BFYndnTEwUxrh5P/PD3R55h1w jXa6OeHmXm0dW536ePFgb6UAmchd9T54YO8+hNux/TzlISHgTQj1QW7ioK0P3K65qM4t HOdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735810215; x=1736415015; 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=ehheSC50hzplOsi8PH5mCgAYHgHrLSe9FGutXVNdUjk=; b=Iz4XpEZmmpSJCdv/2L8yp9l2q2tCkvAbLCB1WogYkCqKCQrYKH8fhAC5DSMuUeqOmS Z7eSEf1uXiFf2Y+X7W/ue/oi3ja17rr1adI+5qdATcgzbSxjF820vLhlQSnxsa0oIdl3 kY5bdRiWVYy68n+7IVheUsNH7/VdyeWeqKpavdA9UlwA+Om9yQI3tskIyJtEv0k4jlF9 EQNm/r2n6SSHQhqElHejh8gLhMqqFs7RM3O///k+a8lgKTK2dWC0gSETDnrSSeyYOuy+ uOmOSdsGK3bpFQ7W74es6tC33PQ7R58urH1wxAtF8Oql9rKhYm215hS3YsAxINufrqPl N2bQ== X-Gm-Message-State: AOJu0YwtJtR0TM/JgRqyY+CEdJBZ0oOabBW9239v6A6rDg8bqzdulTvz InBbIUSqtOnCjii31zzzaBdS+HRQeHT2RG//CJwp2N3T1sSHYsagtfmx4BWVcV9pib1n3XN6DdX +nGTpq5fBuI7Ajk+cOEfh4df2ya0= X-Gm-Gg: ASbGncsiGYiC/dlcQeWbrlPDoc+aZXjWD2icwiF2NSGywsfl+ATDVvYQiAHWnVb+K0J TF4IG+WvgcuL+KcT4CQ9vOh3HmBzBHOJxWC9jvwqMSzzhLs69brXyku94mZRfmdwEt5C/Mb84 X-Google-Smtp-Source: AGHT+IHHU955+9cyKLVpJr5L3kYpkp93g7OqVoVwUws6U3cdksWollr9DBAYLLBh+Ib6ARgtF2/EziYOESVHE2WKmug= X-Received: by 2002:a05:6902:1b84:b0:e4b:fe5:5dc7 with SMTP id 3f1490d57ef6-e538c42758emr34528636276.43.1735810215488; Thu, 02 Jan 2025 01:30:15 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Richard Guo Date: Thu, 2 Jan 2025 18:30:04 +0900 Message-ID: Subject: Re: ERROR: corrupt MVNDistinct entry To: Andrei Lepikhov Cc: PostgreSQL-development 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 Tue, Dec 31, 2024 at 5:40=E2=80=AFPM Richard Guo wrote: > Regarding the back-patch, this patch is a bug fix, which suggests it > should be back-patched. However, it also changes some plans by fixing > the cost estimation. Does anyone know what our usual approach is in > this situation? Although this patch could result in plan changes, it fixes an actual bug, so I've back-patched it to v16. Thanks Richard