Re: [PATCH] Transaction traceability - txid_status(bigint) - Mailing list pgsql-hackers

From David Steele
Subject Re: [PATCH] Transaction traceability - txid_status(bigint)
Date
Msg-id b817967d-e48d-6164-95ee-5da492a7f030@pgmasters.net
Whole thread Raw
In response to Re: [PATCH] Transaction traceability - txid_status(bigint)  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [PATCH] Transaction traceability - txid_status(bigint)  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 3/25/17 12:12 AM, Peter Eisentraut wrote:
>> I'm wondering if this is a perl version/platform issue around
>>
>>     $tx->pump until $stdout =~ /[[:digit:]]+[\r\n]$/;
>>
>> where we're not recognising the required output from psql when we get it.
>>
>> What's in src/test/recovery/tmp_check/log/regress_log_011* ?
>>
>> I couldn't use PostgresNode::psql or PostgresNode::safe_psql here
>> because the session must stay open.
>
> The problem was that psql needs to be called with -X.  Fix committed.

It's not clear to me what remains to be done on this patch.  I feel, at 
the least, that patches 3 and 4 need to be rebased and the status set 
back to "Needs Review".

This thread has been idle for six days.  Please respond with a new patch 
by 2017-04-04 00:00 AoE (UTC-12) or this submission will be marked 
"Returned with Feedback".

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Patch: Write Amplification Reduction Method (WARM)
Next
From: Pavel Stehule
Date:
Subject: Re: Variable substitution in psql backtick expansion