| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Tristan Partin <tristan(at)neon(dot)tech> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: meson: Stop using deprecated way getting path of files |
| Date: | 2023-12-18 06:43:09 |
| Message-ID: | CANWCAZbLArD=Ntuit42ayRJPdDY+f8qrQwzxSM_cy-GkBXN32g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 5, 2023 at 3:27 AM Tristan Partin <tristan(at)neon(dot)tech> wrote:
>
> On Mon Dec 4, 2023 at 2:10 PM CST, Tom Lane wrote:
> > Not sure what you were using, but are you aware that SQL access to the
> > buildfarm database is available to project members? My own stock
> > approach to checking on this sort of thing is like
> >
> > select * from
> > (select sysname, snapshot, unnest(string_to_array(log_text, E'\n')) as l
> > from build_status_log join snapshots using (sysname, snapshot)
> > where log_stage = 'configure.log') ss
> > where l like 'checking for builtin %'
>
> This looks useful. I had no idea about this. Can you send me any
> resources for setting this up? My idea was just to do some web scraping.
+1 -- I was vaguely aware of this, but can't find any mention of
specifics in the buildfarm how-to, or other places I thought to look.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ywgrit | 2023-12-18 06:55:57 | Re: Fix bug with indexes on whole-row expressions |
| Previous Message | John Naylor | 2023-12-18 06:41:35 | Re: [PoC] Improve dead tuple storage for lazy vacuum |