Bruce, I've finished digging for stuff that seems to be appropriate to back-patch for 7.2.4. Do you have time to generate the release notes and brand the release? Attached are the CVS commit messages for all the changes in that branch since 7.2.3.
regards, tom lane 2003-01-26 18:16 tgl * src/backend/commands/user.c (REL7_2_STABLE): Back-patch fixes to detoast pg_group.grolist. 2003-01-26 18:09 tgl * src/backend/access/heap/heapam.c (REL7_2_STABLE): Back-patch fixes to ensure t_ctid always has correct value (prevents some instances of 'No one parent tuple' VACUUM error, and perhaps worse things). 2003-01-26 17:33 tgl * src/: backend/utils/adt/datetime.c, test/regress/expected/timestamp.out, test/regress/expected/timestamptz.out (REL7_2_STABLE): Back-patch fix for alphabetization mistakes in datetime token tables. 2003-01-21 14:51 tgl * src/backend/access/transam/xlog.c (REL7_2_STABLE): Back-patch fix to ensure pg_clog updates are not only written but sync'ed before we consider the checkpoint to be done. 2003-01-21 14:41 tgl * src/backend/utils/adt/geo_ops.c (REL7_2_STABLE): Back-patch fixes for integer overflows in circle_poly(), path_encode(), and path_add() --- from Neil Conway. Also, repair recently-detected errors in lseg_eq(), lseg_ne(), lseg_center(). 2003-01-21 14:38 tgl * src/backend/commands/vacuum.c (REL7_2_STABLE): Back-patch fix for VACUUM being confused by SELECT FOR UPDATE of tuple that was previously outdated by a transaction that later aborted. Also, prevent VACUUM from being called inside function. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster