[Bug]: TimescaleDB regression test cagg_permissions failed on latest PostgreSQL minor release 17.6 and 15.14

[xinxinzhenhuai]

What type of bug is this?

Unexpected error

What subsystems and features are affected?

Other

What happened?

This test could run successfully on 17.5 with no errors. Is there anything wrong with this test?Are we safe to ignore this test?

TimescaleDB version affected

2.21.3

PostgreSQL version used

17.6

What operating system did you use?

RHEL9

What installation method did you use?

Source

What platform did you run on?

On prem/Self-hosted

Relevant log output and stack trace

diff -u /workspace/extensions/timescaledb/tsl/test/expected/cagg_permissions-17.out /workspace/extensions/timescaledb/build/tsl/test/results/cagg_permissions-17.out
     --- /workspace/extensions/timescaledb/tsl/test/expected/cagg_permissions-17.out	2025-08-20 18:05:46.310729886 +0000
     +++ /workspace/extensions/timescaledb/build/tsl/test/results/cagg_permissions-17.out	2025-08-20 19:09:33.667109553 +0000
     @@ -160,7 +160,7 @@
      -- in ts_continuous_agg_watermark are executed
      SET timescaledb.enable_cagg_watermark_constify = OFF;
      SELECT * FROM mat_refresh_test;
     -ERROR:  permission denied for materialized view mat_refresh_test
     +ERROR:  permission denied for view mat_refresh_test
      RESET timescaledb.enable_cagg_watermark_constify;
      SELECT * FROM :materialization_hypertable;
      ERROR:  permission denied for table _materialized_hypertable_2
     + su builduser -c 'pg_ctl stop -D /home/builduser/data_dir'

How can we reproduce the bug?

make installcheck

[akuzm]

Thanks for reporting, this is going to be fixed soon by #8491

[akuzm]

To answer your question, I suppose it's a cosmetic difference that is safe to ignore.

[billyean]

as the pg release note(https://www.postgresql.org/docs/release/15.14/) pointed out. This is expected behavior. Test shall be fixed to catch the error

This has been fixed by making security checks on views occur at the start of planning. That might cause permissions failures to occur earlier than before.