Hi,I'll try to return it to the original thread. I absolutely agree with you. Data loss during migration is an unacceptable situation. And why it's still happening, I don't understand. But issuing messages will require translating it into other languages and complicate the patch. I'm not a program
Hi Thank you all for the helpful tips. Many thanks to Alex Orlov for the test. He works.I made a second version of the patch and took into account all the comments.Patch description: When checking a new cluster, the value of the track_commit_timestamp parameter is determined. If this parameter is s
. They were lost with each migration if users did not manually migrate them. Кому: 'ls' ([email protected]);Копия: [email protected];Тема: Patch for migration of the pg_commit_ts directory;01.10.2025, 17:17, "Hayato Kuroda (Fujitsu)" :Hi,
ve followed all the recommendations.Removed the function. Shortened the test.01. Removed initialization of variables.02. Change03. Removed04. Add ----Кому: 'ls' ([email protected]), [email protected] ([email protected]), [email protected] (amit.kapil...@gma
not run it for the old cluster, but use data from the old_cluster.controldata.chkpnt_newstCommitTsxid control file. But this will be less clear than using the check_track_commit_timestamp_parameter function. The test can be shortened. Кому: 'ls' (ls7...@yandex
Thanks.That's the good news.Thanks to Hayato Kuroda, for the advice.Thanks to everyone who participated in the promotion of the patch. Кому: ls ([email protected]);Копия: Hayato Kuroda (Fujitsu) ([email protected]), [email protected], amit.kapil...@gmai
Hi,Followed all recommendations. Кому: 'ls' ([email protected]);Копия: [email protected], [email protected], [email protected];Тема: Patch for migration of the pg_commit_ts directory;09.10.2025, 11:22, "Hayato Kuroda (Fujitsu)" :Hi,Tha
Hi,I applied the diff file.Deleted the $ts variable. Кому: 'ls' ([email protected]);Копия: [email protected], [email protected], [email protected];Тема: Patch for migration of the pg_commit_ts directory;14.10.2025, 09:27, "Hayato Kuroda (Fujits
Hi. Added a fatal message about an incorrect track_commit_timestamp parameter for new cluster. Update test.Fail check:Checking for new cluster tablespace directories okChecking for pg_commit_ts "track_commit_timestamp" must be "on" but is set to "o
Good afternoon!During pg_upgrade migration, the pg_commit_ts directory is not copied when track_commit_timestamp = on is set. There is a patch in the attachment that fixes this. Contents & Purpose==The patch copies the pg_commit_ts directory of the old cluster and updates the Latest
10 matches
Mail list logo
