From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <munro(at)ip9(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: NOTIFY with tuples |
Date: | 2011-12-14 04:21:19 |
Message-ID: | 27298.1323836479@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Dec 13, 2011 at 6:30 PM, Thomas Munro <munro(at)ip9(dot)org> wrote:
>> I imagine a very simple system like this, somehow built on top of
>> the existing NOTIFY infrastructure:
> I'm not sure whether we'd want something like this in core, so for a
> first go-around, you might want to consider building it as an
> extension. ... I'm not sure you
> need NOTIFY for anything anywhere in here.
Actually, what I'd suggest is just some code to serialize and
deserialize tuples and transmit 'em via the existing NOTIFY payload
facility. I agree that presenting it as some functions would be a lot
less work than inventing bespoke syntax, but what you sketched still
involves writing a lot of communications infrastructure from scratch,
and I'm not sure it's worth doing that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-12-14 04:23:35 | Re: WIP: URI connection string support for libpq |
Previous Message | Tom Lane | 2011-12-14 04:15:30 | Race condition in HEAD, possibly due to PGPROC splitup |