Horton

Re: VLDB Features

Markus Wanner <markus@bluegap.ch>

View thread
From: Markus Schiltknecht <markus@bluegap.ch>
To: josh@agliodbs.com
Cc: pgsql-hackers@postgresql.org, Hannu Krosing <hannu@skype.net>, Simon Riggs <simon@2ndquadrant.com>
Date: 2007-12-12T18:23:49Z
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 →

  1. doc: Fix COPY ON_ERROR option syntax synopsis.

  2. Disallow specifying ON_ERROR option without value.

  3. Rename COPY option from SAVE_ERROR_TO to ON_ERROR

  4. Fix spelling in notice

  5. Add new COPY option SAVE_ERROR_TO

Hi,

Josh Berkus wrote:
> Here's the other VLDB features we're missing:
> 
> Parallel Query

Uh.. this only makes sense in a distributed database, no? I've thought 
about parallel querying on top of Postgres-R. Does it make sense 
implementing some form of parallel querying apart from the distribution 
or replication engine?

> Windowing Functions

Isn't Gavin Sherry working on this? Haven't read anything from him lately...

> Parallel Index Build (not sure how this works exactly, but it speeds Oracle 
> up considerably)

Sounds interesting *turs-away-to-google*

> On-disk Bitmap Index (anyone game to finish GP patch?)

Anybody having an idea of what's missing there (besides good use cases, 
which some people doubt)? Again: Gavin?

> Simon, we should start a VLDB-Postgres developer wiki page.

Thanks, Simon, wiki page looks good!

Regards

Markus