Re: BUG #5669: server process was terminated by exception 0xC0000005

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Geery <andrew(dot)geery(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5669: server process was terminated by exception 0xC0000005
Date: 2010-09-22 17:54:22
Message-ID: 28562.1285178062@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of mi sep 22 13:36:18 -0400 2010:
>> Well, the more general point is what should "SHOW session_authorization"
>> show in an autovacuum process? The fact that Andrew wasn't
>> intentionally doing that doesn't mean that someone else might not try
>> it. I think we can either decide it should be an obviously-illegal
>> value, or try to make it return the name of the cluster-creating
>> superuser. The latter seems like more work than it's worth though.

> +1 for the illegal value.

OK. I just dug through all the other show-hook functions and confirmed
that show_session_authorization is the only one that will dump core if
its variable is NULL, so it looks like we have just one case to fix.
Will get on it once I get my repo back together ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-09-23 00:57:47 Re: BUG #5671: ERROR: out of memory
Previous Message Alvaro Herrera 2010-09-22 17:47:01 Re: BUG #5669: server process was terminated by exception 0xC0000005