Robert Haas wrote: > Well, the history here is pretty weird. In relevant part, here's the > result of cvs log on src/backend/parser/gram.c: > > revision 2.92 > date: 2007/04/17 01:06:27; author: tgl; state: dead; lines: +0 -0 > And remove 'em again ... > ---------------------------- > revision 2.91 > date: 2007/04/17 01:05:07; author: tgl; state: Exp; lines: +0 -12088 > Temporarily re-add derived files, in hopes of straightening out their > CVS status. > ---------------------------- > revision 2.90 > date: 1999/05/07 01:22:54; author: vadim; state: Exp; lines: +6001 -5942 > branches: 2.90.2; > Fix LMGR for MVCC. > Get rid of Extend lock mode. > ---------------------------- > revision 2.89 > date: 1999/03/28 20:32:04; author: vadim; state: Exp; lines: +3292 -3225 > 1. Vacuum is updated for MVCC. > 2. Much faster btree tuples deletion in the case when first on page > index tuple is deleted (no movement to the left page(s)). > 3. Remember blkno of new root page in BTPageOpaque of > left/right siblings when root page is splitted. > ---------------------------- > revision 2.88 > date: 1999/03/20 18:43:49; author: tgl; state: dead; lines: +1 -1 > Remove yacc/lex output files from CVS repository. > > The fact that the file was "modified" twice after being removed at rev > 2.88 seems really wacko. Are you sure that's not contributing to what > we're seeing here?
I think this is the normal behavior when a file is deleted then re-added. In version 2.89 the file was re-added, and its delta is against the pre-deleted version (presumably 2.87). (Actually, even deleted versions can have deltas, so technically the delta in 2.89 is against the "hidden content" of version 2.88. Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers