Re: Indexing on JSONB field not working

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zhihong Zhang <zhihong(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Indexing on JSONB field not working
Date: 2019-12-28 19:15:29
Message-ID: CAMkU=1yPjRSTfTxwSL857jy0MGe9xrsSgphZ9C5B1sEOHbxM0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Dec 27, 2019 at 4:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Zhihong Zhang <zhihong(at)gmail(dot)com> writes:
> >> On Dec 27, 2019, at 12:45 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> >> Can you do `pg_dump -s -t assets ...` to get a full description of the
> table? If you don't want to share the full description, make sure whatever
> simplifications you do to it don't prevent the problem from reproducing.
>
> > I created a new table ‘assets_copy’ with only 3 columns. I can still
> reproduce the problem. The pg_dump output is attached.
>
> I'm a little suspicious of this because it says the table owner is
> "postgres", but you say you're not superuser. Does RDS create a
> non-superuser "postgres" account?
>

Yes, the default setting for RDS is to have a user named "postgres" which
is as-super-as RDS allows you to get.

Cheers,

Jeff

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Zhihong Zhang 2019-12-28 19:59:07 Re: Indexing on JSONB field not working
Previous Message Jeff Janes 2019-12-28 19:10:40 Re: Indexing on JSONB field not working