parameter "wal_sync_method": "open_datasync"
>HINT: Available values: fsync, fdatasync, open_sync.
The open_datasync may not supported by your system. Can you please check what
are types of syncs supported in your system.
Use the pg_test_fsync tool which is present in contrib f
s ,
but version mismatched.
Can you please check is there any other version of postgres present in the
machine?
Regards,
Hari babu.
As the following raised bug is not received by the bugs mailing list.
Forwarding the same to mailing list.
http://www.postgresql.org/message-id/E1USmqv-0006X0-5X@wrigleys.postgresql.o
rg
Please check the above defect needs any handling?
Regards,
Hari babu.
--
Sent via pgsql-bugs mailing
throw away lightly.
I tested the patch, it is working fine.
I have a query regarding the changing of pmState only incase of SIGTERM but
not incase of SIGINT.
Is there any reason to handle like this? or Is it ok to modify the handling
of pmState in SIGTERM same as SIGINT?
Regards,
Hari babu.
if (InArchiveRecovery && IsUnderPostmaster)
{
PublishStartupProcessInformation();
SetForwardFsyncRequests();
kill (PostmasterPid, SIGINT);
SendPostmasterSignal(PMSIGNAL_RECOVERY_STARTED);
pmState = PM_WAIT_BACKENDS;
}
else if (pmState == PM_RUN ||
Regards,
Hari babu.
