pgsql <pgsql@lavabit.com> writes:
> Tom Lane wrote:
>> Um, that's not too helpful, we want to see the string it's pointing at.
> Sorry about that. All statements are calling one of two pl/pgsql
> functions. While that information already helps me a lot, it'll take me
> a while to step through the code. Those functions are outer wrappers
> calling many other procedures.
Well, the stack trace you showed previously indicates that the crash is
happening in the outermost plpgsql function (ie, one called directly
from a client SQL command). However it's certainly true that the crash
might be a consequence of something that had been done a bit earlier in
another function called by this one.
Keep in mind that the crash very likely doesn't happen when you simply
step through the function in isolation. If it is the same as or
related to the previously-fixed bug, it would only happen if a cache
flush event happened at just the wrong time (as a consequence of
sufficiently many concurrent catalog updates issued by other processes).
regards, tom lane