Re: Autovaccuum vs temp tables crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Autovaccuum vs temp tables crash
Date
Msg-id 25504.1550846742@sss.pgh.pa.us
Whole thread Raw
In response to Autovaccuum vs temp tables crash  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Autovaccuum vs temp tables crash  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> The reason for the crash is 6d842be6c11, where Tom added an assert for
> passing null into %s. But I don't think we can blame that patch for the
> problem -- it's passing the NULL there in the first place that's the
> problem.

Indeed; this crash existed on some platforms all along (which means
we'd better back-patch the fix).

> AFAICT the actual drop works fine, it's just the logging that crashes. So
> maybe we should just add a check and make it log something like "<dropped>"
> if pg_namespace_name() returns null?

+1 ... maybe "(dropped)", because we tend to use parens for this sort
of thing, I think.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: psql show URL with help
Next
From: Peter Eisentraut
Date:
Subject: Re: psql show URL with help