Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaKhW-0000s3-Cy for pgsql-admin@arkaria.postgresql.org; Thu, 28 Nov 2019 14:23:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iaKhV-0008FT-5S for pgsql-admin@arkaria.postgresql.org; Thu, 28 Nov 2019 14:23:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaKhU-0008FM-P5 for pgsql-admin@lists.postgresql.org; Thu, 28 Nov 2019 14:23:20 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaKhS-0000jn-2D for pgsql-admin@postgresql.org; Thu, 28 Nov 2019 14:23:20 +0000 Received: by mail-wm1-x341.google.com with SMTP id l1so11167254wme.2 for ; Thu, 28 Nov 2019 06:23:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=Pk+z8s9QHv/slxw68mLEsOO79JwKN3pJbT/aGAQdyGQ=; b=B8HCT738bZcy8YH+QtlyM67pz7eoYW8iAnZKkC2Y2K0EHROmbalMaERw8OjNEhZLPx cpukYhSh1f8H/l3uh+YzpqfEWKmeWDcx1/KBp6nFODwHweG0KXUNihadUmHgIisgu4Wa xo8wlWjOxa0ilP0Pcjo2vbD30toOyiFj9HzTiyqrfLjMlQUAGCQEpcSpW7SCrLkQz7d6 AZZOGFIt6vJfhwIAwkK9nqjKbpNlGEzY/7NUZ5okxdM7VxPIx80fWSz2mMvGYt8/29kv Vr8iIyN9cF5qB+AosxpSLCwfG+lBeWH1OorPWgjKLR6A8fepR6xtNYqdctKOYIO8qGiP S2rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=Pk+z8s9QHv/slxw68mLEsOO79JwKN3pJbT/aGAQdyGQ=; b=a6vt5tzDdWTS83RE7bjXUoKbHaBfremAzWvNxvcH9KWqFXxv8be9IbSUDDf2KQJnFS T6hwIBoubDGQCydNhKBZFr1fnBvW2G6xT43VSx9WS3d4GAMv7zgLdGEjOUbROJ2BbTG4 YiEYuQgCseiLJQSzLviIkugxe65+s4oOIKYsvAPPOKSX6e7YT/fNSSukinu0R1J40GPG gxrXLAPFl/Q6Mpn4MZ4t5UUs6obpTm+8u6c5HQnQgYPnTuphzk5kr/rE9VkwJCIfZ0s4 ksh95F0nCWWpjwvX88wNI2/vM4LxfjtODN4wrzrAutTT3WjqYYJbISAF2BUSt0ZemHrd RCqg== X-Gm-Message-State: APjAAAUsAIXt7zkN5Kpkd9ZYnfv8Ds2PKDndg80o2Ff1JKxWouGkNhuX FucoQH+d0/Y1mDZJbEkouzpJYQ== X-Google-Smtp-Source: APXvYqzM70v/u95WNGTSwYFBjUlpjdYzSs/e+rgtyzgtyAKXpD52DFAhwVAhPmjT1CHgoaOh/jSfGQ== X-Received: by 2002:a1c:4c10:: with SMTP id z16mr9258166wmf.136.1574950996984; Thu, 28 Nov 2019 06:23:16 -0800 (PST) Received: from localhost.localdomain (217-149-168-19.nat.highway.telekom.at. [217.149.168.19]) by smtp.gmail.com with ESMTPSA id 2sm23400081wrq.31.2019.11.28.06.23.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Nov 2019 06:23:15 -0800 (PST) Message-ID: Subject: Re: No result when selecting attstattarget from pg_attribute From: Laurenz Albe To: "William Sescu (Suva)" , "pgsql-admin@postgresql.org" Date: Thu, 28 Nov 2019 15:23:15 +0100 In-Reply-To: <4078c426dbbb4e18a047ec00485adba9@suva.ch> References: <4078c426dbbb4e18a047ec00485adba9@suva.ch> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, 2019-11-28 at 09:55 +0000, William Sescu (Suva) wrote: > Now I create the custom statistics, however, attstattarget is still -1 > > (klb@[local]:55000)[knowledgebase]> CREATE STATISTICS s1 (dependencies) ON a, b FROM t1; > CREATE STATISTICS > > (klb@[local]:55000)[knowledgebase]> select attrelid::regclass as name, attname, attstattarget from pg_attribute where attname in ('a','b'); > name | attname | attstattarget > ------+---------+--------------- > t1 | a | -1 > t1 | b | -1 > (2 rows) > > Am I looking at the wrong view? I am planning to do some upgrades to 12.x, and therefore, I created this little test case > to make sure that I don't forget to set custom statistics on the new version, if there are any. "attstattarget" is set to a value different from -1 if you define a special statistics detail level for the column: ALTER TABLE t1 ALTER a SET STATISTICS 1000; It has nothing to do with extended statistics. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com