Skip site navigation (1) Skip section navigation (2)

bg worker: patch 6 of 6 - ooo messages

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: bg worker: patch 6 of 6 - ooo messages
Date: 2010-07-13 14:31:44
Message-ID: 4C3C78D0.70803@bluegap.ch (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-hackers
Finally, this patch adds the capability to cache out-of-order messages 
for workers within the coordinator process. Unlike the cache of jobs, 
which basically are messages as well, these messages don't trigger a 
job, but might provide additional information or data payload to a 
worker that's already processing a job.

In case of Postgres-R, the very first change set received starts an 
applicator job, while every subsequent change set as well as the final 
commit decision are such ooo-messages, which are forwarded to the same 
worker.

A parallel querying feature might want to use similar ooo messages for 
data payload, forth and back. However, simpler jobs like vacuum don't 
necessarily need this.

Attachment: step6-ooo.diff
Description: text/x-diff (7.5 KB)

pgsql-hackers by date

Next:From: Yeb HavingaDate: 2010-07-13 15:21:07
Subject: Re: explain.c: why trace PlanState and Plan trees separately?
Previous:From: Markus WannerDate: 2010-07-13 14:31:32
Subject: bg worker: patch 5 of 6 - splitting

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group