Re: pgmemcache - Mailing list pgsql-performance

From Tom Lane
Subject Re: pgmemcache
Date
Msg-id 2847.1144975434@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgmemcache  (PFC <lists@peufeu.com>)
Responses Re: pgmemcache  (Christian Storm <christian.storm@gmail.com>)
List pgsql-performance
PFC <lists@peufeu.com> writes:
>     I guess AFTER COMMIT triggers would be like a NOTIFY, but more powerful.

I'll let you in on a secret: NOTIFY is actually a before-commit
operation.  This is good enough because it never, or hardly ever,
fails.  I would argue that anything you want to do in an AFTER COMMIT
trigger could just as well be done in a BEFORE COMMIT trigger; if that's
not reliable enough then you need to fix your trigger.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Blocks read for index scans
Next
From: "patrick keshishian"
Date:
Subject: Re: pg 7.4.x - pg_restore impossibly slow