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

Re: notification payloads

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: notification payloads
Date: 2007-03-27 11:16:45
Message-ID: 4608FD1D.2050008@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Hannu Krosing wrote:
> I find the feature very useful, and have even done some preliminary
> design work for shared memory implementation, where each listener is
> required to copy data to its own privat memory ASAP and notifier waits
> in case there is not enough room in shared memory buffer.
>
> Alas, I have lost my design 3 a4 pages of design notes for organising
> things in fixed-size buffer, but the basic operation data-wise sould be
> as in attached sql file.
>
>
>   

[snip]


This looks somewhat like what I originally had in mind, but discussion 
led to something much simpler. The only thing we need to share is the 
queue. Everything else can be done in the individual backends.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-03-27 11:28:59
Subject: Re: notification payloads
Previous:From: alfranio correia juniorDate: 2007-03-27 11:11:49
Subject: Re: Re: [PATCHES] As proposed the complete changes to pg_trigger and pg_rewrite

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