ERROR: must be superuser to examine "shared_preload_libraries"

[killua001]

When run sql to delete data from the partition table:
delete from ubas_event_info_his_20170327 a where a.data_source not in ('ios','android')

Error raise：
Caused by: org.postgresql.util.PSQLException: ERROR: must be superuser to examine "shared_preload_libraries"

postgresql.conf：
shared_preload_libraries = 'pg_pathman,repmgr_funcs,pg_stat_statements,auto_explain'

[funbringer]

Hi @killua001,

Thank you for your bug report. In fact, pg_pathman is supposed to show you this message:

ERROR: extension conflict has been detected
DETAIL: shared_preload_libraries = "pg_pathman,repmgr_funcs,pg_stat_statements,auto_explain"
HINT: pg_pathman should be the last extension listed in shared_preload_libraries GUC
in order to prevent possible conflicts with other extensions

We'll fix this in no time, but you should definitely follow this hint.

[killua001]

Thank you

[funbringer]

Pushed a fix into master branch.

[killua001]

Hi, @funbringer ,
After I change the shared_preload_libraries parameter to
shared_preload_libraries = 'repmgr_funcs,pg_stat_statements,auto_explain,pg_pathman'

The error "ERROR: must be superuser to examine "shared_preload_libraries" still there.

Can I download the master branch now, or will you provided a hot fix release?

[funbringer]

to @killua001:

Can I download the master branch now, or will you provided a hot fix release?

Could you try a master branch? I'll release a hotfix if it works for you.

[killua001]

I will try the master branch, and run it for one week.
Thank you.

[tarvip]

README says that pg_pathman must be first if using together with pg_stat_statements, but HINT says it should be last, which one is correct?

[funbringer]

to @tarvip:

Thanks, I've fixed readme. Sometimes it's hard to track changes.

pg_pathman should be the last extension.

[funbringer]

to @killua001:

Is everything ok now?

[killua001]

@funbringer
There is no error until now. May be the bug has been fixed .

[funbringer]

@killua001:

Ok, feel free to write us if anything is wrong. You'll be able to post messages in this thread even if the issue is closed.

[killua001]

@funbringer
Will you release a new version to fix this bug?

[funbringer]

I think we'll roll out a bugfix release in 1-2 days (1.3.1).

[killua001]

@funbringer
Thank you!