Re: Bison 3.0 updates

Поиск
Список
Период
Сортировка
От Marti Raudsepp
Тема Re: Bison 3.0 updates
Дата
Msg-id CABRT9RCW9M4ZUHVXKkrYhF8uYs9bYc0-K_d1v-71gbo_NTHfJA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Bison 3.0 updates  (Andrew Dunstan <andrew@dunslane.net>)
Ответы Re: Bison 3.0 updates  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
On Mon, Jul 29, 2013 at 9:15 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> There has to be something between "set in stone and never changes" and
> "auto-updates everything every 24 hours" that would suit us.

Well sure I could change the update frequency. But again, it seems
like delaying the inevitable.

> I'm toying with the idea of a check_upgrade mode for the buildfarm client
> where it wouldn't do a git pull, but would report changes if the build
> result was different from the previous result. You'd run this immediately
> after pulling new changes into your OS. Other, brighter ideas welcome.

What would be the right course of action if check_upgrade fails? Is it
reasonable to expect buildfarm volunteers to downgrade the system and
postpone until the problem is resolved?

Or do you think the member should be removed from the farm until the
build succeeds again? Sounds like worst of both worlds.

Regards,
Marti



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Re: maintenance_work_mem and CREATE INDEX time
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: Bison 3.0 updates