Greetings,
* lejeczek (peljasz@yahoo.co.uk) wrote:
> What is that - as per subject - a symptom of exactly?
Arguably, a poor restore command being used ...
PostgreSQL will request .history files when doing recovery and will keep
requesting them, by default, until it finds that one isn't there- it
will then target the last timeline that it found to perform replay to
(target timeline = latest). We do also look for .history files when
going through the promotion process and similarily will keep checking
for timeline files until we don't find one and then that's the timeline
we will move to for the promotion and we'll then immediately push a new
.history file into the archive to 'claim' that timeline.
Basically, it's not an error and it's entirely intentional that it works
that way and your restore command probably shouldn't be complaining
about it really (and that's where the actual 'No such file or directory'
bit is coming from- not from PG itself).
> I get that there was an issue, but with more details explained. Perhaps
> there are docs which explain that?
Much more likely that there wasn't actually any issue...
> When it happens I take slave down and do _pg_basebackup_ off the master -
> but is there a more "civilized" way to "push" the slave back in sync, maybe
> without taking slave off-line?
Not following this bit at all. There being a message about PG not
finding a .history file during restore or promotion isn't actually an
indication of anything having gone wrong or that the replica is out of
sync. In other words, I don't know that you needed to actually do
anything. Is there some reason you think you did need to do something
beside that message being in the log..?
Thanks,
Stephen