Re: refactoring comment.c
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-08-28T01:26:02Z
Lists: pgsql-hackers
Excerpts from Robert Haas's message of vie ago 27 18:07:55 -0400 2010: > On Fri, Aug 27, 2010 at 5:57 PM, Kevin Grittner > <Kevin.Grittner@wicourts.gov> wrote: > > Robert Haas <robertmhaas@gmail.com> wrote: > >> I suppose this is unhappy because it things elog(ERROR) might > >> return? > > > > If I set these fields right in front of the elog(ERROR) the warnings > > go away for me. (Hopefully this observation will make up, to some > > extent, for my earlier brain fart.) > > I set them right after the ERROR so that those statements needn't > actually be executed. Didn't we inject some smarts so that the compiler would notice that elog(ERROR) doesn't return? Why isn't it working here? -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support