On Wed, Jan 11, 2012 at 11:38 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> The obvious first use case for this is for cache invalidation. > > Yeah, upthread Simon pointed out that propagating notifies would be > useful for flushing caches in applications that watch the database in a > read-only fashion. I grant that such a use-case is technically possible > within the limitations of a slave server; I'm just dubious that it's a > sufficiently attractive use-case to justify the complexity and future > maintenance costs of the sort of designs we are talking about. Or in > other words: so far, cache invalidation is not the "first" use-case, > it's the ONLY POSSIBLE use-case. That's not useful enough. Many people clearly do think this is useful. I personally don't think it will be that complex. I'm willing to review and maintain it if the patch works the way we want it to. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
