Re: BUG #5669: server process was terminated by exception 0xC0000005 - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5669: server process was terminated by exception 0xC0000005
Date
Msg-id 1285177595-sup-6709@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #5669: server process was terminated by exception 0xC0000005  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5669: server process was terminated by exception 0xC0000005
List pgsql-bugs
Excerpts from Tom Lane's message of mié sep 22 13:36:18 -0400 2010:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Excerpts from Tom Lane's message of mié sep 22 13:03:06 -0400 2010:
> >> Wouldn't an empty string be acceptable?  SQL doesn't allow zero-length
> >> identifiers, so this couldn't be confused with any really-valid value.
>
> > I dunno really -- what is this value used for, anyway?  If it's just to be
> > able to generate the SHOW table which is then parsed to obtain the
> > fulltext configuration, seems OK.
>
> 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.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-bugs by date:

Previous
From: Jeff Davis
Date:
Subject: Re: UNLISTEN bug
Next
From: Tom Lane
Date:
Subject: Re: BUG #5669: server process was terminated by exception 0xC0000005