Horton

Re: VLDB Features

decibel <decibel@decibel.org>

View thread
From: Decibel! <decibel@decibel.org>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2007-12-18T16:41:20Z
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

On Dec 12, 2007, at 1:26 PM, Markus Schiltknecht wrote:
> 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*...


Except that doing something in-machine is often far simpler than  
trying to go cross-machine, especially when that something is a  
background reader.

Let's walk before we run. :)
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828