Re: Error creating gin index on jsonb columns

We can't test a non-concurrent index build in production - but your word is
just as good.

We only see this on some of production databases. We did not see it in QA
testing. But we will try to get a test case in QA.

Is this categorized as a bug specific to GIN indexes or a PostgreSQL bug in
general?

-glenn

On Fri, Oct 16, 2015 at 7:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Glenn Zhu <gzhu(at)medallia(dot)com> writes:
> > Currently, after hitting the error, the indexes were still created but
> > marked with status of "invalid"
>
> That's just what CREATE INDEX CONCURRENTLY would do with any error.
> (It might be worth checking whether a non-CONCURRENTLY build hits the
> same error, though I'm betting it will.)
>
> > If it's a bug, what information would be needed to trigger a bug fix?
>
> A reproducible test case would move things along quite a bit; without that
> we're just guessing.
>
> > Is there a formal channel?
>
> Well, you could move the thread to pgsql-bugs but you might as well
> keep it where it is.
>
> regards, tom lane
>

--
Glenn Zhu
SaaS Operations | ❖ Medallia, Inc.