From: | Olleg Samoylov <splarv(at)ya(dot)ru> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Asynchronous Trigger? |
Date: | 2018-04-27 10:46:29 |
Message-ID: | 8172161524825989@web45j.yandex.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
<div text="#000000" bgcolor="#FFFFFF">
Try to look at PGQ from SkyTools.<br />
<br />
<div>On 2018-03-30 01:29, Cory Tucker wrote:<br />
</div>
<blockquote type="cite" cite="mid:CAG_=8kAdbc_DoJWy11xh5J8b+v-ZWSt3Ty-1Ffdn4scgq3wK6Q(at)mail(dot)gmail(dot)com">
<div dir="ltr">
<div>Is it possible to have the execution of a trigger (or any
function) not block the completion of the statement they are
associated with?</div>
<div><br />
</div>
<div>A pattern I had hoped to implement was to do a quick update
of rows that signaled they needed attention, and then an async
per-row trigger would come and do the maintenance (in this
case, make an expensive materialized view).</div>
<div><br />
</div>
<div>Any suggestions welcome.</div>
<div><br />
</div>
<div>thanks!</div>
<div>--Cory</div>
</div>
</blockquote>
<br />
</div>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/html | 1009 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Lavoie | 2018-04-27 11:39:06 | Fwd: Failed rpm package signature checks with reposync |
Previous Message | Olivier Macchioni | 2018-04-27 10:28:31 | Re: Locks analysis after-the-fact |