pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in

pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in

pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in

pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in

pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in

pgsql: Fix outdated bit in README.tuplock

2024-11-21 Thread Álvaro Herrera
Fix outdated bit in README.tuplock Apparently this information has been outdated since first committed, because we adopted a different implementation during development per reviews and this detail was not updated in the README. This has been wrong since commit 0ac5ad5134f2 introduced the file in