From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Use the terminology "WAL file" not "log file" more consistently. |
Date: | 2022-09-15 10:19:25 |
Message-ID: | CALj2ACWFPf-JT+_pBnZS8F9RGWD+59mmjGd2WZ6JtOau_A31oA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Thu, Sep 15, 2022 at 2:54 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> On 2022-Sep-15, Tom Lane wrote:
>
> > Yeah, the lowest-tech solution is to accept either spelling of
> > the description string. But I'm not very happy with the whole
> > approach right now. We should have an implementation that isn't
> > dependent on how user-friendly strings are spelled.
>
> We already discussed this, a mere 12 years ago,
> https://postgr.es/m/1283373680-sup-9235@alvh.no-ip.org
> for exactly the same reason.
>
> Let's just do it?
Thanks for pointing it out. It seems like a good idea IMO. I think
pg_resetwal also needs the --machine approach. As --machine approach
needs a good amount of refactoring and discussion, I still think we
can make buildfarm happy by fixing a proposed solution [1]. Perhaps,
we can start a new thread for --machine approach.
Thoughts?
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-09-15 13:08:21 | Re: pgsql: Doc: Explain about Column List feature. |
Previous Message | Joe Conway | 2022-09-15 10:12:40 | Re: pgsql: Use the terminology "WAL file" not "log file" more consistently. |