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

Re: notification payloads

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: notification payloads
Date: 2007-03-26 18:07:40
Message-ID: 4341.1174932460@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Why have the name on each message?  Presumably names are going to be few
> compared to the total number of messages, so maybe store the names in a
> separate hash table and link them with a numeric identifier.  That gives
> you room for a lot more messages.

That can be done by the application, if its notify payloads are such
that that's a useful optimization.  However it seems entirely possible
to me that the payload strings might be nonrepeating and the overhead
of a separate table completely wasted.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-03-26 18:15:39
Subject: Re: pg_index updates and SI invalidation
Previous:From: Pavan DeolaseeDate: 2007-03-26 18:01:20
Subject: Re: pg_index updates and SI invalidation

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