Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1

Hello,
There is one update:

The tests plpgsql and prepared_xacts do run on AIX 7.1 with PostgeSQL
8.2.11 and 8.2.23 without a problem.

Bye
Rainer

On 24.02.2014 11:29, Rainer Tammer wrote:
> Hello,
> I am still using a 8.2 PortgresSQL for an older application.
> I have compiled 8.2.11 (same as on the old server) and
> 8.2.23 (latest 8.2) on AIX 7.1 TL3 SP1 (latest level) with
> the IBM C/C++ V12 compiler.
>
> Unfortunate I see the following errors:
>
> ...
> 2014-02-24 10:07:30 CET LOG: received fast shutdown request <--- here
> 2014-02-24 10:07:30 CET LOG: shutting down
> 2014-02-24 10:07:30 CET LOG: database system is shut down
> 2014-02-24 10:07:36 CET LOG: database system was shut down at
> 2014-02-24 10:07:30 CET
> 2014-02-24 10:07:36 CET LOG: checkpoint record is at 0/E9F073E0
> 2014-02-24 10:07:36 CET LOG: redo record is at 0/E9F073E0; undo record
> is at 0/0; shutdown TRUE
> 2014-02-24 10:07:36 CET LOG: next transaction ID: 0/7161900; next OID:
> 39134
> 2014-02-24 10:07:36 CET LOG: next MultiXactId: 1; next MultiXactOffset: 0
> 2014-02-24 10:07:36 CET LOG: database system is ready
> 2014-02-24 10:08:35 CET LOG: received fast shutdown request <--- here
> 2014-02-24 10:08:35 CET LOG: shutting down
> 2014-02-24 10:08:35 CET LOG: database system is shut down
> 2014-02-24 10:10:45 CET LOG: database system was shut down at
> 2014-02-24 10:08:35 CET
> 2014-02-24 10:10:45 CET LOG: checkpoint record is at 0/E9F07430
> 2014-02-24 10:10:45 CET LOG: redo record is at 0/E9F07430; undo record
> is at 0/0; shutdown TRUE
> 2014-02-24 10:10:45 CET LOG: next transaction ID: 0/7161950; next OID:
> 39134
> 2014-02-24 10:10:45 CET LOG: next MultiXactId: 1; next MultiXactOffset: 0
> 2014-02-24 10:10:45 CET LOG: database system is ready
>
> I had set a higher log level to see all client statements.
> Unfortunately I could see in the log file that when the
> fast shutdown was executed that there where no running statements.
>
> I never had a problem on AIX 5.3. Do you have any ideas??
>
>
> So I have decided to give 9.2.7 a try. During the make check I have
> found two failures - to be more precisely two hangs.
>
> I have changed parallel_schedule to run most test sequential.
> The following tests do show a problem:
>
>
> 1. problem
>
> plpgsql.out <- this test hangs in statement_timeout.
>
> ...
> end$$ language plpgsql;
> set statement_timeout to 2000;
> select blockme(); <- hang
>
>
> 2. problem
>
> prepared_xacts.out <- this test hangs in statement_timeout.
>
> ...
> -- pxtest3 should be locked because of the pending DROP
> set statement_timeout to 2000;
> SELECT * FROM pxtest3; <- hang
>
> These tests do not move forward even if I wait 10 minutes.
>
> So my conclusion is that the statement_timeout does not work as expected.
>
> Bye
> Rainer
>
>
>