pgsql: Adjust m68k spinlock code to avoid duplicate in-line and - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Adjust m68k spinlock code to avoid duplicate in-line and
Date
Msg-id 20050826144735.C7845D7A03@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Adjust m68k spinlock code to avoid duplicate in-line and not-in-line
definitions on recent Linux systems, per Martin Pitt.

Modified Files:
--------------
    pgsql/src/backend/storage/lmgr:
        s_lock.c (r1.37 -> r1.38)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/s_lock.c.diff?r1=1.37&r2=1.38)
    pgsql/src/include/storage:
        s_lock.h (r1.135 -> r1.136)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/s_lock.h.diff?r1=1.135&r2=1.136)

pgsql-committers by date:

Previous
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Back-port recent MIPS and M68K spinlock improvements to 8.0
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: The idea of using _strncoll() on Windows doesn't work.