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

pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date: 2010-01-05 02:34:03
Message-ID: 20100105023403.6BF21753FB7@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Log Message:
-----------
Remove too-smart-for-its-own-good optimization of not overwriting the output
files when they haven't changed.  This confuses make because the build fails
to update the file timestamps, and so it keeps on doing the action over again.

Modified Files:
--------------
    pgsql/src/backend/catalog:
        Catalog.pm (r1.1 -> r1.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/Catalog.pm?r1=1.1&r2=1.2)
        genbki.pl (r1.1 -> r1.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/genbki.pl?r1=1.1&r2=1.2)

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-01-05 02:34:07
Subject: Re: pgsql: Get rid of the need for manual maintenance of the initial
Previous:From: Tom LaneDate: 2010-01-05 02:20:42
Subject: Re: pgsql: Get rid of the need for manual maintenance of the initial

pgsql-committers by date

Next:From: Andrew DunstanDate: 2010-01-05 02:34:07
Subject: Re: pgsql: Get rid of the need for manual maintenance of the initial
Previous:From: Tom LaneDate: 2010-01-05 02:20:42
Subject: Re: pgsql: Get rid of the need for manual maintenance of the initial

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