Horton

Re: VLDB Features

Markus Wanner <markus@bluegap.ch>

View thread
From: Markus Schiltknecht <markus@bluegap.ch>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Date: 2007-12-12T19:26:16Z
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,

Josh Berkus wrote:
> Sure.  Imagine you have a 5TB database on a machine with 8 cores and only one 
> concurrent user.  You'd like to have 1 core doing I/O, and say 4-5 cores 
> dividing the scan and join processing into 4-5 chunks.

Ah, right, thank for enlightenment. Heck, I'm definitely too focused on 
replication and distributed databases :-)

However, there's certainly a great deal of an intersection between 
parallel processing on different machines and parallel processing on 
multiple CPUs - especially considering NUMA architecture. 
*comes-to-think-again*...

>> Isn't Gavin Sherry working on this? Haven't read anything from him
>> lately...
> 
> Me neither.  Swallowed by Greenplum and France.

Hm.. good for him, I guess!

Regards

Markus