Re: refactoring comment.c
От | Alvaro Herrera |
---|---|
Тема | Re: refactoring comment.c |
Дата | |
Msg-id | 1282958532-sup-2306@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: refactoring comment.c (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: refactoring comment.c
|
Список | 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
В списке pgsql-hackers по дате отправления: