Re: Acclerating INSERT/UPDATE using UPS - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Acclerating INSERT/UPDATE using UPS
Date
Msg-id 45E0DAD4.9090106@commandprompt.com
Whole thread Raw
In response to Re: Acclerating INSERT/UPDATE using UPS  (Christopher Browne <cbbrowne@acm.org>)
Responses Re: Acclerating INSERT/UPDATE using UPS  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Christopher Browne wrote:
> A long time ago, in a galaxy far, far away, kawasima@cs.tsukuba.ac.jp (Hideyuki Kawashima) wrote:
>> I appreciate your great suggestion!
>> It is great honor for me if Sigres will be merged to PostgreSQL.
>> Since the changes of Sigres from PostgreSQL-8.2.1 are not many,
>> and moreover, all of changes are surrounded with #ifdef SIGRES --- #endif,
>> incorporating Sigres into PostgreSQL would be easy.
> 
> You should consider submitting a patch for this against CVS HEAD.
> 
> And actually, I'd think it a better idea to define a GUC variable and
> use that to control whether Sigres is active or not.
> 
> At the more sophisticated end of the spectrum, you might set things up
> so that it could be activated/deactivated at runtime by a superuser.
> 
> At the less sophisticated end, it might need to be configured in
> postgresql.conf...

Whatever happen with this?

Joshua D. Drake


-- 
     === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997            http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/



pgsql-hackers by date:

Previous
From: "Chad Wagner"
Date:
Subject: Re: conversion efforts (Re: SCMS question)
Next
From: Warren Turkal
Date:
Subject: Re: conversion efforts (Re: SCMS question)