9.6.7 -> 9.6.8 analyze worker behaviour changed? - Mailing list pgsql-bugs

From Marius Vaičiulis
Subject 9.6.7 -> 9.6.8 analyze worker behaviour changed?
Date
Msg-id 005401d3b6d2$fd471d80$f7d55880$@com
Whole thread Raw
Responses Re: 9.6.7 -> 9.6.8 analyze worker behaviour changed?  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-bugs

Hi,

 

Updated our server from 9.6.7 to 9.6.8 (PostgreSQL 9.6.8 on x86_64-pc-linux-gnu (Debian 9.6.8-1.pgdg80+1), compiled by gcc (Debian 4.9.2-10+deb8u1) 4.9.2, 64-bit), and not really funny messages started to appear in the logs:

 

2018-03-08 12:59:06 EET     ERROR:  relation "spatial_ref_sys" does not exist at character 23

2018-03-08 12:59:06 EET     QUERY:  SELECT proj4text FROM spatial_ref_sys WHERE srid = 4326 LIMIT 1

2018-03-08 12:59:06 EET     CONTEXT:  automatic analyze of table "gpt_v2.customer101.t_customer"

 

That table (not the only one) uses the functional indexes, one of which uses postgis functions, so the failing call comes from within postgis function written in C. No changes were noticed in selects, updates, no errors except that. I did some kind of workaround to make that problem go away by doing ALTER FUNCTION … SET SEARCH_PATH TO public; for every postgis function used in the indexes. public is where postgis extension is located (from long time ago).

 

Not sure what to do next, is this a bug, is my realization considered to be a bug, or workaround is a bug? Maybe some configuration parameter was (were) introduced, that I have missed?

 

Thanks for any input.

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15101: function set search_path = '' breaks dump/restore
Next
From: David Rowley
Date:
Subject: Re: 9.6.7 -> 9.6.8 analyze worker behaviour changed?