Re: Duplicate history file?

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: sfrost(at)snowman(dot)net
Cc: michael(at)paquier(dot)xyz, rjuju123(at)gmail(dot)com, tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp, masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Duplicate history file?
Date: 2021-06-16 03:07:22
Message-ID: 20210616.120722.2079142998904720856.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Wed, 16 Jun 2021 12:04:03 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Ok, if we follow the direction that we are responsible for ensuring
> that every user has reliable backups, I don't come up with proper
> description about that.
>
> We could list several "requirement" like "do sync after copy", "take a
> checksum for all files then check it periodically" or other things but
> what is more important things to list here, I think, is "how we run
> the archive_command".
>
> Doesn't the following work for now?
>
> (No example)
>
> - "%f is replace by ... %p is .., %r is ... in archive_command"
>
> - We call the archive_command for every wal segment which is finished.
>
> - We may call the archive_command for the same file more than once.
>
> - We may call the archive_command for different files with the same
> name. In this case server is working incorrectly and need a
> check. Don't overwrite with the new content.
>
> - We don't offer any durability or integrity on the archived
> files. All of them is up to you. You can use some existing
> solutions for archiving. See the following links.

Of course, there should be some descriptions about error handling
along with.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-06-16 03:08:00 Re: disfavoring unparameterized nested loops
Previous Message Kyotaro Horiguchi 2021-06-16 03:04:03 Re: Duplicate history file?