Skip site navigation (1) Skip section navigation (2)

pgsql: Now that much of walreceiver has been pulled back into the

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Now that much of walreceiver has been pulled back into the
Date: 2010-01-20 18:54:27
Message-ID: 20100120185427.923A97541B9@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Now that much of walreceiver has been pulled back into the postgres
binary, revert PGDLLIMPORT decoration of global variables. I'm not sure
if there's any real harm from unnecessary PGDLLIMPORTs, but these are all
internal variables that external modules really shouldn't be messing
with. ThisTimeLineID still needs PGDLLIMPORT.

Modified Files:
--------------
    pgsql/src/include/libpq:
        pqsignal.h (r1.39 -> r1.40)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/pqsignal.h?r1=1.39&r2=1.40)
    pgsql/src/include/replication:
        walreceiver.h (r1.3 -> r1.4)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/replication/walreceiver.h?r1=1.3&r2=1.4)
    pgsql/src/include/storage:
        ipc.h (r1.80 -> r1.81)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/ipc.h?r1=1.80&r2=1.81)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-01-20 19:43:40
Subject: pgsql: Write a WAL record whenever we perform an operation without
Previous:From: Heikki LinnakangasDate: 2010-01-20 11:59:55
Subject: Re: pgsql: Rethink the way walreceiver is linked into the backend. Instead

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group