From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: .ready and .done files considered harmful |
Date: | 2021-05-05 05:33:41 |
Message-ID: | CAFiTN-t5SDFkZQZH2ybghF9bHgT9yqfGRfkxeERp2e0WObOcNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 4, 2021 at 10:12 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > Is this true? that only when we have to wait for the next file to be
> > ready we got for scanning? If I read the code in
> > "pgarch_ArchiverCopyLoop", for every single file to achieve it is
> > calling "pgarch_readyXlog", wherein it scans the directory every time.
> > So I did not understand your point that only when it needs to wait for
> > the next .ready file it need to scan the full directory. It appeared
> > it always scans the full directory after archiving each WAL segment.
> > What am I missing?
>
> It's not true now, but my proposal would make it true.
Okay, got it. Thanks.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2021-05-05 05:38:12 | Re: AlterSubscription_refresh "wrconn" wrong variable? |
Previous Message | Dilip Kumar | 2021-05-05 05:32:05 | Re: Small issues with CREATE TABLE COMPRESSION |