On 19 July 2018 at 04:30, Jeremy Finzel 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 fu
On Wed, Jul 18, 2018 at 3:05 PM, Tom Lane wrote:
> Jeremy Finzel writes:
> > I have a background worker running SQL functions, and I believe I have
> > noticed that when I do things like change function definitions, or even
> add
> > tables, the background worker does not pick up the schema chan
Jeremy Finzel writes:
> I have a background worker running SQL functions, and I believe I have
> noticed that when I do things like change function definitions, or even add
> tables, the background worker does not pick up the schema changes until I
> restart the worker.
Maybe you need some Accept
I have a background worker running SQL functions, and I believe I have
noticed that when I do things like change function definitions, or even add
tables, the background worker does not pick up the schema changes until I
restart the worker.
Is this expected behavior? If I use background workers i
