pgsql: Fix DetermineSafeOldestOffset for the case where there are no mx

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix DetermineSafeOldestOffset for the case where there are no mx
Date: 2015-05-11 02:03:16
Message-ID: E1Yrd3s-0001an-0a@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix DetermineSafeOldestOffset for the case where there are no mxacts.

Commit b69bf30b9bfacafc733a9ba77c9587cf54d06c0c failed to take into
account the possibility that there might be no multixacts in existence
at all.

Report by Thomas Munro; patch by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/312747c224be4c0a880b5172a010e980f8b654ca

Modified Files
--------------
src/backend/access/transam/multixact.c | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2015-05-11 02:48:21 pgsql: Advance the stop point for multixact offset creation only at che
Previous Message Tom Lane 2015-05-11 01:14:08 Re: pgsql: Code review for foreign/custom join pushdown patch.