Re: VLDB Features

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: pgsql-hackers@postgresql.org

Cc: Simon Riggs <simon@2ndquadrant.com>

Date: 2007-12-11T18:53:11Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: Fix COPY ON_ERROR option syntax synopsis.
- f6f8ac8e75c9 17.0 landed
Disallow specifying ON_ERROR option without value.
- a6d0fa5ef840 17.0 landed
Rename COPY option from SAVE_ERROR_TO to ON_ERROR
- b725b7eec431 17.0 landed
Fix spelling in notice
- 58fbbc9d683c 17.0 landed
Add new COPY option SAVE_ERROR_TO
- 9e2d8701194f 17.0 landed

Simon.

> VLDB Features I'm expecting to work on are
> - Read Only Tables/WORM tables
> - Advanced Partitioning
> - Compression
> plus related performance features

Just so you don't lose sight of it, one of the biggest VLDB features we're 
missing is fault-tolerant bulk load.  Unfortunately, I don't know anyone 
who's working on it.

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco