ROBUSTNESS
- Massive overhaul of pg_dump: make use of dependency information from
pg_depend to determine a safe dump order.| Defaults and check
constraints can be emitted either as part of a table or domain
definition, or separately if that's needed to break a dependency loop.
Lots of old half-baked code for controlling dump order removed.
Performance work has also occurred to address some regressions in
performance this caused.
(Tom)
- Changes to ALTER .. SET PATH allows ordered dumps to restore without
error - pg_restore options to select restore order now removed - not
needed (Tom)
- In backend/access/transam/ add warning to AtEOXact_SPI() to catch
cases where the current txn has been committed without SPI_finish()
being called first. Allows detection of resource leaks... (Joe)
- psql memory allocation is being cleaned up, using safer calls
(Bruce/Neil)
- GetNewTransactionId() logic sequence now enhanced to stay intact even
at final stage of resource failure conditions, such as running out of
disk space etc (Tom)
- Add checks for close() and fclose() failure, applicable to some
filesystems. Various locations affected in backend,initdb,copy (Tom)
- A header record was added to each WAL file, to allow them to be
reliably identified. We now avoid splitting WAL records across segment
files, and we now make WAL entries for file creation, deletion, and
truncation. This work should give the basics for building the true PITR
implementation (J.R., Patrick, Tom)
- Also, add support for making XLOG_SEG_SIZE configurable at compile
time, similarly to BLCKSZ, possibly useful for smaller installations.
(Tom)
