| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Update README.tuplock |
| Date: | 2015-05-25 18:11:10 |
| Message-ID: | E1YwwqE-0005pG-1X@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Update README.tuplock
Multixact truncation is now handled differently, and this file hadn't
gotten the memo.
Per note from Amit Langote. I didn't use his patch, though.
Also update the description of infomask bits, which weren't completely up
to date either. This commit also propagates b01a4f6838 back to 9.3 and
9.4, which apparently I failed to do back then.
Branch
------
REL9_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/833c3961d9f22b46c32eeb9c4e73d334864994ed
Modified Files
--------------
src/backend/access/heap/README.tuplock | 47 ++++++++++++++++++--------------
1 file changed, 26 insertions(+), 21 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-25 18:13:16 | pgsql: Explain CHECK constraint handling in postgres_fdw's IMPORT FOREI |
| Previous Message | Andrew Dunstan | 2015-05-25 15:48:09 | pgsql: Clean up and simplify jsonb_concat code. |