PostgreSQL Refactoring

REFACTORING AND OTHER CODE CHANGES

- Remove the explicit casting of NULL literals to a pointer in a wide
variety of code locations (Neil)

- Add operator strategy and comparison-value datatype fields to ScanKey.
Remove the 'strategy map' code - Passing the strategy number to the
index AM directly should now be simpler and faster. Changes to
ScanKeyEntryInitialize() API touches quite a lot of files. (Tom)

- nbtree function _bt_first is now substantially changed/simplified
(Tom)

- Change PG_DELAY from msec to usec and use it consistently rather than
select(). Add Win32 Sleep() for delay. (Bruce)

- Supporting relaxing of ALTER...SET PATH requires changing the API for
GUC assign_hook functions, which touches a lot of places (Tom)

- initdb has now been completely re-written from shell script to C
(Andrew)

- Add some code to guc.c to allow backwards compatibility for server
config parameters. Variable renaming is now more easily possible, since
parameters can potentially be referenced by both their old and new names
in SHOW and SET commands. (Tom)

- Remove the long-dead 'persistent main memory' storage manager (mm.c),
since it seems quite unlikely to ever get resurrected. (Tom)

- Add configure support for determining UINT64_FORMAT, the appropriate
snprintf format for uint64 items (Tom)

- Put another layer of indirection between the compute_stats functions
and the actual data storage.| This change would eventually allow us to
compute the values on-the-fly, for example using dynamic data sampling
techniques when ANALYZE output is not available... (Tom)

- In src/backend/access/ we have major changes in heap, nbtree, transam
and common code

- Almost all files src/backend/commands have changes; mostly robustness

- JDBC interface has been moved out into its own project to improve the
focus on this popular and important area of client code.

About this Entry

This page contains a single entry by published on March 3, 2004 4:05 PM.

PostgreSQL New Functionality was the previous entry in this blog.

PostgreSQL Major Impacts is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.