pg.ddx.io  pgpartman/pg_partman GitHub issues and pull requests  
help / color / mirror / Atom feed
From: AlexeyShalaev (@AlexeyShalaev) <noreply+AlexeyShalaev@github.com>
To: pgpartman/pg_partman <noreply+pgpartman-pg_partman@github.com>
Subject: Re: [pgpartman/pg_partman] PR #879: fix: partition_data_time() compares the control column in its own type
Date: Mon, 26 Oct 2026 06:24:35 +0000
Message-ID: <gh-pgpartman-pg_partman-879-c6409669900@github.com> (raw)
In-Reply-To: <gh-pgpartman-pg_partman-879@github.com>
References: <gh-pgpartman-pg_partman-879@github.com>

One more data point, plus a quick way to check which code a database is running.

The new test passes on a fresh 551 install on PG 14, 17 and 18 under UTC, America/New_York, America/Los_Angeles and Pacific/Kiritimati.

This tells you whether the loaded `partition_data_time()` is the pre-fix one: the 5.5.0 version still declares `v_control_exact_type`, and the new one doesn't.

```sql
SELECT n.nspname, pg_get_functiondef(p.oid) LIKE '%v_control_exact_type%' AS pre_fix
FROM pg_proc p JOIN pg_namespace n ON n.oid = p.pronamespace
WHERE p.proname = 'partition_data_time';
```

If that says `true` after `make install`, either the extension wasn't updated in that database or `make install` went to a different PostgreSQL than the one the test ran against (easy to hit on macOS with more than one `pg_config` on the PATH).

view thread (12+ messages)  latest in thread

Message-ID: <gh-pgpartman-pg_partman-879-c6409669900@github.com>
Permalink:  ../gh-pgpartman-pg_partman-879-c6409669900@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox