Re: How to run a task continuously in the background - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: How to run a task continuously in the background
Date
Msg-id 20190719195313.36d5xgcub7kh2vda@hjp.at
Whole thread Raw
In response to Re: How to run a task continuously in the background  (Rory Campbell-Lange <rory@campbell-lange.net>)
Responses Re: How to run a task continuously in the background  (Rory Campbell-Lange <rory@campbell-lange.net>)
List pgsql-general
On 2019-07-17 12:34:41 +0100, Rory Campbell-Lange wrote:
> We make extensive use of postgresql 'contacting' an external process,
> but our use case involves many databases in a cluster rather than many
> schemas. Also we don't have to deal with cancelling the external
> process. We chose this architecture to avoid many postgresql
> connections for LISTEN/NOTIFY.
>
> We use a pgmemcache interface trigger to update memcached with a
> notification of the database holding items to be flushed.

Memcached is a cache. It will delete old items if storage is full (or if
they expire). Is this not a problem in your case or did you make sure
that this cannot happen?

        hp

--
   _  | Peter J. Holzer    | we build much bigger, better disasters now
|_|_) |                    | because we have much more sophisticated
| |   | hjp@hjp.at         | management tools.
__/   | http://www.hjp.at/ | -- Ross Anderson <https://www.edge.org/>

Attachment

pgsql-general by date:

Previous
From: Alexandru Lazarev
Date:
Subject: Re: pg_advisory_lock lock FAILURE / What does those numbers mean(process 240828 waits for ExclusiveLock on advisory lock [1167570,16820923,3422556162,1];)?
Next
From: Stephen Frost
Date:
Subject: Re: Rearchitecting for storage