| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Peter Eisentraut <peter(at)eisentraut(dot)org>, mikael(dot)kjellstrom(at)gmail(dot)com, buildfarm-members(at)lists(dot)postgresql(dot)org, rosset(dot)filipe(at)gmail(dot)com |
| Subject: | Re: |
| Date: | 2025-03-08 12:18:59 |
| Message-ID: | 1416b4f1-3199-4aba-9b62-5569aa96c708@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members |
On 2025-03-07 Fr 2:56 PM, Tom Lane wrote:
> =?UTF-8?Q?Mikael_Kjellstr=C3=B6m?= <mikael(dot)kjellstrom(at)mksoft(dot)nu> writes:
>> OK. I've updated it now but skipped the extra compiler details. I guess
>> it goes onto some approve queue somewhere or takes a while before it
>> updates the information?
> I believe it shows up immediately on the members page:
>
> https://buildfarm.postgresql.org/cgi-bin/show_members.pl
>
> Individual build runs capture the current setting, so you won't
> see a change in existing run logs; the next run on a branch
> will update that.
>
>
Yes, pretty much. There's a table called personality that captures the
changes with a timestamp, and the status pages show the personality with
the latest timestamp earlier than the the run.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2025-03-30 14:44:11 | Server downtime noon .. 4pm UTC March 31 |
| Previous Message | Mikael Kjellström | 2025-03-07 21:14:06 | Re: |