I'd like to suggest that when we upgrade the buildbot master, we use a Postgres backend instead of sqlite:
http://docs.buildbot.net/latest/manual/cfg-global.html#postgres
This is for better performance.
Since postgres is involved, this would require coordination with the Python infra team.
-- Craig
On Fri, Oct 6, 2017 at 3:36 PM, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
I'd like to suggest that when we upgrade the buildbot master, we use a Postgres backend instead of sqlite:
http://docs.buildbot.net/latest/manual/cfg-global.html#postgres
Since it's such a simple change, we can just factor db_uri out to
local.py, defaulting to sqlite, and we can switch to postgres at our
leisure later. I'm not concerned about resetting the database to do
so.
-- Zach
On Fri, Oct 6, 2017 at 1:42 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
On Fri, Oct 6, 2017 at 3:36 PM, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
I'd like to suggest that when we upgrade the buildbot master, we use a Postgres backend instead of sqlite:
http://docs.buildbot.net/latest/manual/cfg-global.html#postgres
Since it's such a simple change, we can just factor
db_uriout tolocal.py, defaulting to sqlite, and we can switch to postgres at our leisure later. I'm not concerned about resetting the database to do so.
Sounds good to me. I just wanted to raise the issue early on in the process, so as to keep the python infra team in the loop and not leave them blindsided.
-- Craig
participants (2)
-
Craig Rodrigues -
Zachary Ware