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

Re: Is there any problem with pg_notify and memory consumption?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Per-Olov Esgard <Per-Olov(dot)Esgard(at)micronic-mydata(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Is there any problem with pg_notify and memory consumption?
Date: 2011-05-27 15:43:13
Message-ID: 13715.1306510993@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On Fri, May 27, 2011 at 4:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think the right fix is to make sure that ProcessCompletedNotifies
>> saves and restores the call-time CurrentMemoryContext.

> Can we put a WARNING in there if we try to commit while in TopMemoryContext?

That has nothing to do with it ...

			regards, tom lane

In response to

pgsql-general by date

Next:From: Gaetano GiuntaDate: 2011-05-27 15:59:31
Subject: adding applications to the stack builder
Previous:From: Simon RiggsDate: 2011-05-27 15:42:12
Subject: Re: Is there any problem with pg_notify and memory consumption?

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