Re: Background worker/idle sessions and caching - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Background worker/idle sessions and caching
Date
Msg-id CAMsr+YGyjeRUJpbbANLuXG6zpmYT_0ZTRkxPKLxTCyrMhzNgVQ@mail.gmail.com
Whole thread Raw
In response to Re: Background worker/idle sessions and caching  (Jeremy Finzel <finzelj@gmail.com>)
List pgsql-hackers
On 19 July 2018 at 04:30, Jeremy Finzel <finzelj@gmail.com> wrote:

My use case is similar to the example of worker_spi.  A plpgsql function runs every 1 minute and processes records in audit tables in order to update fact tables with records that have changed.  I noticed for example renaming a column in the function was not picked up, and I had to restart the workers to reset the cache.

relation_openrv and relation_openrv_extended call AcceptInvalidationMessages when the lockmode is not NoLock. 

Don't we use those when doing SPI queries? No time to check right now, try setting some breakpoints or tracing through.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Possible bug in logical replication.
Next
From: Michael Paquier
Date:
Subject: Re: Possible bug in logical replication.