| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |
| Date: | 2016-04-30 00:36:45 |
| Message-ID: | 20160430003645.vl66pksujc52cupq@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-04-30 02:28:22 +0200, Andreas Seltenreich wrote:
> This sounds like it should work to capture more context when the
> Assertion fails the next time. I have to purge the catalogs a bit
> though to avoid stopping early on boring core dumps. Most of them are
> currently caused by acl.c using text for syscache lookups and triggering
> an NAMEDATALEN assertion.
>
> E.g.: select has_language_privilege('smithsmithsmithsmithsmithsmithsmithsmithsmithsmithsmithsmithsmith', smith');
Yuck. We got to fix those. Does anybody remember how these functions
came to use text instead of name for things that pretty clearly should
have accepted name (i.e. the objects not the priv string)?
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-04-30 00:37:31 | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |
| Previous Message | Andreas Seltenreich | 2016-04-30 00:34:35 | Re: [sqlsmith] Failed assertion in BecomeLockGroupLeader |