Re: New Object Access Type hooks - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: New Object Access Type hooks
Date
Msg-id 74B3B4DC-9909-40BB-B1DD-B4E0BA90765D@enterprisedb.com
Whole thread Raw
In response to Re: New Object Access Type hooks  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New Object Access Type hooks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> On Mar 22, 2022, at 9:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 3/22/22 11:26, Mark Dilger wrote:
>>> culicidae is complaining:
>>> 2022-03-22 14:53:27.198 UTC [2167008][not initialized][:0] FATAL:  test_oat_hooks must be loaded via
shared_preload_libraries
>
>> That seems quite weird. I'm not sure how it's getting loaded at all if
>> not via shared_preload_libraries
>
> After checking culicidae's config, I've duplicated this failure
> by building with EXEC_BACKEND defined.  So I'd opine that there
> is something broken about the method test_oat_hooks uses to
> decide if it was loaded via shared_preload_libraries or not.
> (Note that the failures appear to be coming out of auxiliary
> processes such as the checkpointer.)
>
> As a quick-n-dirty fix to avoid reverting the entire test module,
> perhaps just delete this error check for now.

Ok, done as you suggest:



—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company




Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: New Object Access Type hooks
Next
From: Nikolay Shaplov
Date:
Subject: Re: [PATCH] New [relation] option engine