On 25 March 2017 at 07:31, Peter Eisentraut
<peter.eisentr...@2ndquadrant.com> wrote:
> On 3/24/17 02:27, Craig Ringer wrote:
>> On 24 March 2017 at 02:29, Robert Haas <robertmh...@gmail.com> wrote:
>>> On Tue, Mar 21, 2017 at 11:35 PM, Craig Ringer <cr...@2ndquadrant.com>
>>> wrote:
>>>> Changes made per discussion.
>>>
>>> Committed 0001.
>>
>> Much appreciated.
>>
>> Here's the 2nd patch rebased on top of master, with the TAP test
>> included this time. Looks ready to go.
>
> I'm experiencing hangs in the new t/011_crash_recovery.pl test. It
> seems to hang after the first call to SELECT txid_current();.
if you add
note "txid is $xid";
after
+chomp($xid);
does it report the xid?
Alternately, can you see a 'psql' process and a backend doing a SELECT
when it stops progressing?
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
