Arseny Sher c1a040447d walproposer: send valid timeline_start_lsn in v2 (#10994) ...

## Problem

https://github.com/neondatabase/neon/pull/10647 dropped
timeline_start_lsn from protocol messages as it can be taken from term
history. In v2 0 was sent in the placeholder. However, until safekeepers
are deployed with that PR they still use the value, setting
timeline_start_lsn to 0, which confuses WAL reading; problem appears
only when compute includes 10647 but safekeepers don't.

ref
https://neondb.slack.com/archives/C04DGM6SMTM/p1740577649644269?thread_ts=1740572363.541619&cid=C04DGM6SMTM

## Summary of changes

Send real value instead of 0 in v2.

2025-02-26 17:38:44 +00:00

..

neon

walproposer: send valid timeline_start_lsn in v2 (#10994)

2025-02-26 17:38:44 +00:00

neon_rmgr

Remove unused static function

2024-10-07 23:49:11 +03:00

neon_test_utils

Use smgrexists() instead of access() to enforce uniqueness of generated relfilenumber (#7992)

2024-07-23 18:41:55 +03:00

neon_utils

Be able to get number of CPUs (#3774)

2023-03-10 19:00:20 +02:00

neon_walredo

chore(compute): Postgres 17.3, 16.7, 15.11 and 14.16 (#10771)

2025-02-13 13:28:05 +00:00

.dir-locals.el

Copy editor config for the neon extension from PostgreSQL (#8009)

2024-06-11 23:19:18 +03:00

.editorconfig

Copy editor config for the neon extension from PostgreSQL (#8009)

2024-06-11 23:19:18 +03:00

typedefs.list

Refotmat pgxn code, add typedefs.list that was used

2022-09-14 08:14:05 +03:00