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 1ikfPE-0006y4-BB for pgsql-bugs@arkaria.postgresql.org; Fri, 27 Dec 2019 02:31:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ikfPB-0003Ta-LT for pgsql-bugs@arkaria.postgresql.org; Fri, 27 Dec 2019 02:31:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ikfPB-0003TT-92 for pgsql-bugs@lists.postgresql.org; Fri, 27 Dec 2019 02:31:09 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ikfP4-00062M-37 for pgsql-bugs@lists.postgresql.org; Fri, 27 Dec 2019 02:31:07 +0000 Received: by mail-wr1-x443.google.com with SMTP id z7so24911155wrl.13 for ; Thu, 26 Dec 2019 18:31:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=CtU6Ht9NzYHSWK28e5BtSNG0rxTjA7aBREoLjfFQ9HM=; b=TWyn0+VR/W13Gd1YM3mqDpZTkb5aaaoyfoJV7qaga0PplABG5gtfKX1xNGM23yzY9n F3KG0hGqKBZyxPG2E8DHLOlqIiakZBP6y429LvhHu01Zz+6qhXNeZLs4f8jBfxqJbziz 7k/Fzrz2rqaI7+roRVfMZtNuD/1GMubtS/LZO1phCEJCz+hpd11Crjyap+HHNKluK9dC I97wD2W0ewjC/cRUb+x4dMldOjUj/G3AjST4+rSfPSmHVBuSILQuqy+rKb6+6sTEO+41 jnuHmygaSKIodagDcyTZwet7IEDVKHuWjc4LYREczTnu34l1GEy1Be4F6fqFhYoIXl4R sNjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=CtU6Ht9NzYHSWK28e5BtSNG0rxTjA7aBREoLjfFQ9HM=; b=CziteTWKQsvp8edSORXoeApllFVvo3wDIssP/FcC/SOUNe8moYkg07sxW1QUyGm/st 6OcEGvgg3f6TOsN27RK+3WFuF0ZCbnZO/Ixg3tJWu6fisoJU+4/8WZkiQVYm5YqcLcRj iSsIw/VHYTPKuWjoLx22bOv+UXekhS7PIxMWNjTpBOhdx7eLto8W0A6drP9NpCxm0ITw d77QQIWf9MYA1l0dPV+JcknnzBvz3aaAqykJrv8be8t3vRh+8K8uAtt2hkFdV1R8Px44 drFTsWvMVwTWqAnRJj6sXHbez63ACDKX7KZz+7DMp1akVu72kSJVSezQlsYPOVP6MttT RuNQ== X-Gm-Message-State: APjAAAU37Yj4PbLFGjing91W+jmzn53ERpcjtjhhAFYynwAcQfzhpx+a OZx13A+2XRiEqhDrjJpgwC8TNQ== X-Google-Smtp-Source: APXvYqxL6JF0/oIo0PEVy+kqk/steAIuiOuLMiN1kAiPqbMlacMm805GoGqTSShKu/S9doipStyu2Q== X-Received: by 2002:a5d:6390:: with SMTP id p16mr8277082wru.170.1577413860631; Thu, 26 Dec 2019 18:31:00 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id u1sm9852545wmc.5.2019.12.26.18.30.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Dec 2019 18:30:59 -0800 (PST) Date: Fri, 27 Dec 2019 03:30:59 +0100 From: Tomas Vondra To: Zhihong Zhang Cc: Tom Lane , Jeff Janes , pgsql-bugs Subject: Re: Indexing on JSONB field not working Message-ID: <20191227023059.gsvib26ufgpjbwky@development> References: <83E6A3F7-B1B4-4AD6-905A-BE11D244D35A@gmail.com> <4910.1577386715@sss.pgh.pa.us> <0A83C661-EDBB-43C8-9CBB-FB1E321A15CB@gmail.com> <12042.1577393358@sss.pgh.pa.us> <20191226234124.wuarzcbdq5z5msiy@development> <9485.1577404294@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Dec 26, 2019 at 06:57:52PM -0500, Zhihong Zhang wrote: >I created the index myself using the same account. Should I be the owner? > But Tom explicitly said "owner of the index's table" so it's not important who created the index. But it's easy to check the owner of tables (e.g. using \d+ in psql). BTW please reply in-line (instead of top-posting), it's easier to follow the discussion that way. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services