From: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> |
---|---|
To: | Don Seiler <don(at)seiler(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, <rjuju123(at)gmail(dot)com> |
Subject: | Re: ERROR: invalid memory alloc in Pg 9.6.6 |
Date: | 2018-04-14 08:14:27 |
Message-ID: | 35628c09-fe12-de0c-7cb3-24dc4dc3b86f@anayrat.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 04/13/2018 06:13 PM, Don Seiler wrote:
> On Fri, Apr 13, 2018 at 11:09 AM, Stephen Frost <sfrost(at)snowman(dot)net
> <mailto:sfrost(at)snowman(dot)net>> wrote:
>
> If you can reliably reproduce this with either pg_dump or psql, then the
> next step would perhaps be jumping in with gdb to see where that error
> is being hit..
>
>
> I forgot to follow-up yesterday. It seems like my issue was caused by a bug with
> the pg_qualstats extension that I was using in conjuction with the POWA
> extension. There was already a similar issue reported on their tracker
> at https://github.com/powa-team/powa/issues/104
>
> It seems that high TPS stress testing on Wednesday afternoon triggered the bug.
> When the stress testing tailed off, the error messages stopped happening and I
> was able to run pg_dump without errors. I removed those extensions shortly
> after. The authors have put out a bug fix but I can't use this system to test
> their fix and my sandbox isn't available for the same HA server stress test that
> we were doing on Wednesday.
>
> Don.
>
Hello,
FIY, a new version including bug fix, has been released two days ago :
https://github.com/powa-team/pg_qualstats/releases/tag/1.0.4
Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Chandru Aroor | 2018-04-15 17:28:41 | Error when using Download as CSV |
Previous Message | Don Seiler | 2018-04-13 16:13:20 | Re: ERROR: invalid memory alloc in Pg 9.6.6 |