>> We don't want change checkpoint interval during recovery, that means
>> we cannot cnosider archive_timeout at the fist checkpointer after
>> recovery ends. So I think that the suggestion from Fujii-san is the
>> direction.
>+1
>If this idea has some problems, we can revisit Daisuke-san's idea.
Fujii-san, thank you for comments.
>The cause of this problem is that the checkpointer's sleep time is calculated
>from both checkpoint_timeout and archive_timeout during normal running,
>but calculated only from checkpoint_timeout during recovery. So Daisuke-san's
>patch tries to change that so t
Thank you for comments.
>Unfortunately the diff command in your test script doesn't show me
>anything, but I can understand what you are thinking is a problem,
>maybe.
I'm sorry but I might have confused you... I explain how to use my test script.
I use diff command to check if the archiver has s
Hi,
I found the bug about archive_timeout parameter.
There is the case archive_timeout parameter is ignored after recovery works.
[Problem]
When the value of archive_timeout is smaller than that of checkpoint_timeout
and recovery works, archive_timeout is ignored in the first WAL archiving.
Once
Hi,
I found wrong message output when ECPG preprocessed some SQL commands .
For example, ECPG application has following command, ECPG outputs "unsupported
feature will be passed to server".
---
EXEC SQL CREATE SCHEMA IF NOT EXISTS hollywood;
---
I attached sample code to reprod
