Reimplement planner's handling of MIN/MAX aggregate optimization (again).
Instead of playing cute games with pathkeys, just build a direct
representation of the intended sub-select, and feed it through
query_planner to get a Path for the index access. This is a bit slower
than 9.1's previous meth
Log Message:
---
Fix pointer arithmetic in ora_sinit().
Modified Files:
--
orafce:
shmmc.c (r1.17 -> r1.18)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/shmmc.c?r1=1.17&r2=1.18)
--
Sent via pgsql-committers mailing list (pgsql-committers@pos
When two base backups are started at the same time with pg_basebackup,
ensure that they use different checkpoints as the starting point. We use
the checkpoint redo location as a unique identifier for the base backup in
the end-of-backup record, and in the backup history file name.
Bug spotted by F