v3.42.72: Fix Large DB Mode not applying when changing profiles

Critical fix: Large DB Mode settings (reduced parallelism, increased locks)
were not being reapplied when user changed resource profiles in Settings.

This caused cluster restores to fail with 'out of shared memory' errors on
low-resource VMs even when Large DB Mode was enabled.

Now ApplyResourceProfile() properly applies LargeDBMode modifiers after
setting base profile values, ensuring parallelism stays reduced.

Example: balanced profile with Large DB Mode:
- ClusterParallelism: 4 → 2 (halved)
- MaxLocksPerTxn: 2048 → 8192 (increased)

This allows successful cluster restores on low-spec VMs.

bin/README.md

@@ -4,8 +4,8 @@ This directory contains pre-compiled binaries for the DB Backup Tool across mult
 
 ## Build Information
 - **Version**: 3.42.50
-- **Build Time**: 2026-01-18_17:52:44_UTC
+- **Build Time**: 2026-01-18_20:14:09_UTC
-- **Git Commit**: f9ff45c
+- **Git Commit**: b305d13
 
 ## Recent Updates (v1.1.0)
 - ✅ Fixed TUI progress display with line-by-line output

internal/config/config.go

@@ -445,6 +445,12 @@ func (c *Config) ApplyResourceProfile(profileName string) error {
 
 	// Apply profile settings
 	c.ResourceProfile = profile.Name
+	
+	// If LargeDBMode is enabled, apply its modifiers
+	if c.LargeDBMode {
+		profile = cpu.ApplyLargeDBMode(profile)
+	}
+	
 	c.ClusterParallelism = profile.ClusterParallelism
 	c.Jobs = profile.Jobs
 	c.DumpJobs = profile.DumpJobs