deploy to multiple databases we got exactly the same error.
I did try to set maintenance_work_mam to 4GB and still the same error
occurred.
Thank you.
-glenn
--
Glenn Zhu
SaaS Operations | ❖ Medallia, Inc.
reported are from large tables, with number of rows between 150 to 350
millions.
What would you need in terms of test cases?
Thank you very much.
-glenn
On Fri, Oct 16, 2015 at 6:28 AM, Tom Lane wrote:
> Glenn Zhu writes:
> > We are getting an error on the following statement:
> &g
ad" values? Maybe I shall drop all these indexes.
If it's a bug, what information would be needed to trigger a bug fix? Is
there a formal channel?
Thanks.
-glenn
On Fri, Oct 16, 2015 at 6:43 AM, Tom Lane wrote:
> Glenn Zhu writes:
> > We are currently running 9.4.4. 9.4.5 n
ug in
general?
-glenn
On Fri, Oct 16, 2015 at 7:02 AM, Tom Lane wrote:
> Glenn Zhu 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
We will follow your instructions and get back to you.
Thank you Tom. Much appreciated!
-glenn
On Fri, Oct 16, 2015 at 7:16 AM, Tom Lane wrote:
> Glenn Zhu writes:
> > Is this categorized as a bug specific to GIN indexes or a PostgreSQL bug
> in
> > general?
>
> My gu
