Nathan Bossart 01731eeeaa 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		2024-10-07 13:51:03 -05:00
..
expected	Restrict accesses to non-system views and foreign tables during pg_dump.	2024-08-05 06:05:25 -07:00
sql	Restrict accesses to non-system views and foreign tables during pg_dump.	2024-08-05 06:05:25 -07:00
.gitignore
connection.c	Make postgres_fdw request remote time zone 'GMT' not 'UTC'.	2024-04-21 13:46:20 -04:00
deparse.c	Fix deparsing of Consts in postgres_fdw ORDER BY	2024-03-11 12:28:11 +13:00
Makefile
option.c	Fix Y2038 issues with MyStartTime.	2024-10-07 13:51:03 -05:00
postgres_fdw--1.0--1.1.sql
postgres_fdw--1.0.sql
postgres_fdw.c	postgres_fdw: Avoid "cursor can only scan forward" error.	2024-07-19 13:15:05 +09:00
postgres_fdw.control
postgres_fdw.h
shippable.c