Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state |
| Дата | |
| Msg-id | 1296083282.14137.8.camel@vanquo.pezone.net обсуждение |
| Ответ на | Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Re: [COMMITTERS] pgsql: Get rid of the global variable holding the error state
|
| Список | pgsql-hackers |
On ons, 2011-01-26 at 17:47 -0500, Tom Lane wrote: > Peter Eisentraut <peter_e@gmx.net> writes: > > On lör, 2011-01-22 at 16:36 -0500, Tom Lane wrote: > >> Peter Eisentraut <peter_e@gmx.net> writes: > >>> Get rid of the global variable holding the error state > > >> The buildfarm doesn't like this patch one bit. > > > I have verified your adjustments and fixed up the rest. > > I was a bit disturbed by the fact that fixing only one of the four > variant files was enough to turn the whole buildfarm green. Are the > other three cases even needed anymore? If so, how can we get some > coverage on them? This is explained in plpython/expected/README. As you can see there, it would need some careful attention from buildfarm code and participants to cover all that.
В списке pgsql-hackers по дате отправления: