You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Paquier 173b56f1ef Add flush option to pg_logical_emit_message() ... Since its introduction, LogLogicalMessage() (via the SQL interface pg_logical_emit_message()) has never included a call to XLogFlush(), causing it to potentially lose messages on a crash when used in non-transactional mode. This has come up to me as a problem while playing with ideas to design a test suite for what has become 039_end_of_wal.pl introduced in bae868caf2 by Thomas Munro, because there are no direct ways to force a WAL flush via SQL. The default is false, to not flush messages and influence existing use-cases where this function could be used. If set to true, the message emitted is flushed before returning back to the caller, making the message durable on crash. This new option has no effect when using pg_logical_emit_message() in transactional mode, as the record's flush is guaranteed by the WAL record generated by the transaction committed. Two queries of test_decoding are tweaked to cover the new code path for the flush. Bump catalog version. Author: Michael Paquier Reviewed-by: Andres Freund, Amit Kapila, Fujii Masao, Tung Nguyen, Tomas Vondra Discussion: https://postgr.es/m/ZNsdThSe2qgsfs7R@paquier.xyz		2 years ago
..
expected	Add flush option to pg_logical_emit_message()	2 years ago
specs	Remove incidental md5() function uses from several tests	2 years ago
sql	Add flush option to pg_logical_emit_message()	2 years ago
t	Pre-beta mechanical code beautification.	2 years ago
.gitignore	Improve isolation tests infrastructure.	8 years ago
Makefile	Fix catalog lookup with the wrong snapshot during logical decoding.	3 years ago
logical.conf	Stabilize streaming tests in test_decoding.	3 years ago
meson.build	Update copyright for 2023	3 years ago
test_decoding.c	Add BEGIN/COMMIT for transactional messages during decoding.	2 years ago