Re: Small proposal to improve out-of-memory messages - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Small proposal to improve out-of-memory messages
Date
Msg-id 20180331133607.gbtc2wot3rnsewar@alvherre.pgsql
Whole thread Raw
In response to Small proposal to improve out-of-memory messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Small proposal to improve out-of-memory messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> In the wake of commit 442accc3f one might think that the message should
> also include the context "identifier" if any.  But I'm specifically not
> proposing that, because of the point made in the discussion of that patch
> that some identifier strings might contain security-sensitive query
> excerpts.  Now that that commit has required all context "names" to be
> compile-time constants, it's hard to see how there could be any security
> downside to showing them in a user-visible message.

How about using errdetail_log() to include the context identifier?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: WIP: a way forward on bootstrap data
Next
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning