Hi Tom
Richard Huxton wrote:
Tim Tassonis wrote:
Hi Tom
Tom Lane wrote:
Tim Tassonis <timtas@xxxxxxxx> writes:
The strange thing is, even with loglevel debug5, I don't get any log
message indicating that postgres is even trying to call the command.
Then it isn't, because there are definitely log messages, which were
specifically put there for the purpose of recording the fully-expanded
archive command string:
I must be, as I increased the debug level and that actually took
place. I did get more log messages.
Is there anything else that could prevent the archiving from taking
place, without giving any message?
Did you check Tom's suggestion that you haven't got a duplicate
postgresql.conf somewhere?
As I said, other changes in the config file did have an effect, so that
hardly can be the issue.
Bye
Tim
