From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Can we include capturing logs of pgdata/pg_upgrade_output.d/*/log in buildfarm |
Date: | 2024-02-25 16:18:20 |
Message-ID: | CALDaNm1XuM-w7Up7fHMocB3RYC+gHEEJZ5RSePB6U263GQNX-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 15 Feb 2024 at 08:36, vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> On Thu, 15 Feb 2024 at 07:24, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> >
> > On Wed, Feb 14, 2024 at 03:51:08PM +0530, vignesh C wrote:
> > > First regex is the testname_clusterinstance_data, second regex is the
> > > timestamp used for pg_upgrade, third regex is for the text files
> > > generated by pg_upgrade and fourth regex is for the log files
> > > generated by pg_upgrade.
> > >
> > > Can we include these log files also in the buildfarm?
> > >
> > > [1] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-02-10%2007%3A03%3A10
> > > [2] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2023-12-07%2003%3A56%3A20
> >
> > Indeed, these lack some patterns. Why not sending a pull request
> > around [1] to get more patterns covered?
>
> I have added a few more patterns to include the pg_upgrade generated
> files. The attached patch has the changes for the same.
> Adding Andrew also to get his thoughts on this.
I have added the following commitfest entry for this:
https://commitfest.postgresql.org/47/4850/
Regards,
Vignesh
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2024-02-25 16:18:31 | Preserve subscription OIDs during pg_upgrade |
Previous Message | Tom Lane | 2024-02-25 16:16:07 | Re: Running the fdw test from the terminal crashes into the core-dump |