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 1sCoWz-008K6c-TR for pgsql-general@arkaria.postgresql.org; Thu, 30 May 2024 22:45:59 +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 1sCoWz-006sQr-Mt for pgsql-general@arkaria.postgresql.org; Thu, 30 May 2024 22:45:57 +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 1sCoWz-006sQi-BF for pgsql-general@lists.postgresql.org; Thu, 30 May 2024 22:45:57 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCoWw-002jZZ-RY for pgsql-general@postgresql.org; Thu, 30 May 2024 22:45:56 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-52b7dc424acso1430393e87.0 for ; Thu, 30 May 2024 15:45:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717109151; x=1717713951; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=C+ipu0qQtlKHylZynvKMpNoRCFwr+G7xNCiYkllVJa4=; b=JaoJv74KmKnzuUEoLxE3jxLL020e3+9v+K6msAmxG7pVFU7bX24ePz5F5o0YIqYW1Z 5gSOBEvCh9KhaVaOw0uIQ+BBoyBsSvmRTn2lgkMh78jL+L/jspEKnzhtOjHPlkFjvEh9 7y8w0eYeb1dvw14wNPUCMIECIgInSHb9jh9MHOjQpcj/2G+BHV0KCA8f37zvzkiilU9V zjjTzdp3Y1QhXtj0GheA/8/QXTjPJfw2rMXAJVBrhip564eRYDhIiRpcLWEo4GlAJT6f w8dcF7ZxLr6Ra1qtl7loAfGxq+6GstNoLtvA4z0VMIR+RmJs8X1aRbXeYe7F2+YzRole /m6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717109151; x=1717713951; h=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=C+ipu0qQtlKHylZynvKMpNoRCFwr+G7xNCiYkllVJa4=; b=Lckp81CCJ1KYCZEEuukY/7RyhBNRp4+qQ8IlrO+y+XF3UHwj7y7cdCUyv9pMUyreRq 6tasNCFAbmVRwCdYDqApE2//Y5R1dCYEnBbplFKemMTikdt2mB2GD6Jt6TAZk24dQ4TY GPAxroPVKjWxsZ5fmiFPTmmXFin7utlEL85gaUFB6qHyQc7HBNX2NOLkz5cYx/4BXXo3 vooTwrvagLNiI5wqKP3syrG5omBr5IJO2Ea4FAH2D/N8Gbe3vSlNV7ZCNwgKihlfgxOH U1RnF9GWEySBT5ET4BQtw6Ghv19MQwZflBWx/4wJEGJk1Ar/iwukiZYpsussHNt104Dm i1gw== X-Gm-Message-State: AOJu0YyeiAWZhPP8124RpXU9/tZsNwHKsG6ce0bOHjh0KO4AAJNIulmI LmcF7M7nOa2WkArLmYqN8olp4+cQJPkRZM3GrcsfdlXyCid6wWXCo2Pdzq+uvgEzPpln8VNk0oC l/Bps3aMRULj+XAMGNh5IUdLG7co= X-Google-Smtp-Source: AGHT+IF/E59AmpLAjGOaaUeNIIAaA2A+0k+DyeI0GOGDkFM0/L3pfxg7+RZum81SIabxudkp9wKrEoY5E+qO3MSmnrM= X-Received: by 2002:a05:6512:2144:b0:51d:9ce:c282 with SMTP id 2adb3069b0e04-52b896bf72fmr14808e87.46.1717109151373; Thu, 30 May 2024 15:45:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Rowley Date: Fri, 31 May 2024 10:45:24 +1200 Message-ID: Subject: Re: How to delete column level Stats/Histogram To: "Wong, Kam Fook (TR Technology)" Cc: "pgsql-general@postgresql.org" Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 31 May 2024 at 09:28, Wong, Kam Fook (TR Technology) wrote: > Is there a way to delete a specific column level stats/histogram. The following approach does not work. > > alter table abc alter column bg_org_partner set statistics 0; > analyze abc; You'd have to: DELETE FROM pg_statistic WHERE starelid = 'abc'::regclass and staattnum = (SELECT attnum FROM pg_attribute WHERE attrelid = 'abc'::regclass AND attname = 'bg_org_partner'); to get rid of it. David