pgsql: Don't initialize TLI variable to -1, as TimeLineID is unsigned.

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't initialize TLI variable to -1, as TimeLineID is unsigned.
Date: 2012-07-14 18:30:51
Message-ID: E1Sq77D-0000zp-4q@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't initialize TLI variable to -1, as TimeLineID is unsigned.

This was causing a compiler warning with Solaris compiler. Use 0 instead.
The variable is initialized just for the sake of tidyness and/or debugging,
it's not used for anything before setting it to a real value.

Per report and suggestion from Peter Eisentraut.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/2686da9db2aec19763ff2dfe5c034da8fb5eb382

Modified Files
--------------
src/backend/replication/walreceiver.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-07-15 17:29:13 pgsql: Prevent corner-case core dump in rfree().
Previous Message Jan Urbański 2012-07-14 14:50:06 Re: Re: [COMMITTERS] pgsql: Fix mapping of PostgreSQL encodings to Python encodings.