pgsql: Workaround for RecoverPreparedTransactions()
Workaround for RecoverPreparedTransactions()
Force overwriteOK = true while we investigate deeper fix
Proposed by Tom Lane as temporary measure, accepted by me
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/546c13e11b29a5408b9d6a6e3cca301380b47f7f
Modified Files
--------------
src/backend/access/transam/twophase.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
On 4/23/17 17:14, Simon Riggs wrote:
Workaround for RecoverPreparedTransactions()
Force overwriteOK = true while we investigate deeper fix
This is causing a compiler warning. What is the time line on
reverting/amending this?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
On 26 April 2017 at 15:47, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
On 4/23/17 17:14, Simon Riggs wrote:
Workaround for RecoverPreparedTransactions()
Force overwriteOK = true while we investigate deeper fix
This is causing a compiler warning. What is the time line on
reverting/amending this?
I was just working on it actually. Soon. Today.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers