mirror of
				https://github.com/postgres/postgres.git
				synced 2025-11-03 09:13:20 +03:00 
			
		
		
		
	Fix Y2038 issues with MyStartTime.
Several places treat MyStartTime as a "long", which is only 32 bits wide on some platforms. In reality, MyStartTime is a pg_time_t, i.e., a signed 64-bit integer. This will lead to interesting bugs on the aforementioned systems in 2038 when signed 32-bit integers are no longer sufficient to store Unix time (e.g., "pg_ctl start" hanging). To fix, ensure that MyStartTime is handled as a 64-bit value everywhere. (Of course, users will need to ensure that time_t is 64 bits wide on their system, too.) Co-authored-by: Max Johnson Discussion: https://postgr.es/m/CO1PR07MB905262E8AC270FAAACED66008D682%40CO1PR07MB9052.namprd07.prod.outlook.com Backpatch-through: 12
This commit is contained in:
		@@ -522,7 +522,7 @@ process_pgfdw_appname(const char *appname)
 | 
			
		||||
				appendStringInfoString(&buf, application_name);
 | 
			
		||||
				break;
 | 
			
		||||
			case 'c':
 | 
			
		||||
				appendStringInfo(&buf, "%lx.%x", (long) (MyStartTime), MyProcPid);
 | 
			
		||||
				appendStringInfo(&buf, "%" INT64_MODIFIER "x.%x", MyStartTime, MyProcPid);
 | 
			
		||||
				break;
 | 
			
		||||
			case 'C':
 | 
			
		||||
				appendStringInfoString(&buf, cluster_name);
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user