From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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:47:01 |
Message-ID: | 1285177595-sup-6709@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Excerpts from Tom Lane's message of mié sep 22 13:36:18 -0400 2010:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-22 17:54:22 | Re: BUG #5669: server process was terminated by exception 0xC0000005 |
Previous Message | Jeff Davis | 2010-09-22 17:40:22 | Re: UNLISTEN bug |