so the problem was transient, pgadmin4 launged earlier.
on the other hand, my entire server configuraton has
vanished, which seems suboptimal.
richard
On Mon, 27 Oct 2025 20:23:34 -0400 Richard Welty
wrote ---
the package contains a web app and a desktop app. i have historica
On Tue, Oct 28, 2025 at 2:36 AM Giriraj Sharma
wrote:
> Would daily range partitioning by effective_date (≈ 1000 partitions for 3
> years) be the right long-term approach here?
>
If you are querying based on dates, yes. Does not need to be daily, could
do monthly for example. A retention policy
On 10/28/25 03:25, Wim Rouquart wrote:
Internal
I used the output from DBeaver, guess it acted up. Here’s the output
from psql:
1) As side note, find a different client to use then DBeaver. I have
seen many Postgres questions on Stack Overflow where the answer was, use
something other then
Could you run the SELECT on pg_index after the REINDEX to see if there is
any difference?
On Tue, 2025-10-28 at 12:06 +0530, Giriraj Sharma wrote:
> We are running into query planner instability on an append-only table that
> records daily commit information.
> The workload is heavily skewed toward the current day’s data, and query
> performance deteriorates periodically until we run
Internal
I used the output from DBeaver, guess it acted up. Here’s the output from psql:
select * from pg_index where indexrelid = 'idx_376814_primary'::regclass;
-[ RECORD 1 ]---+
indexrelid | 2006873
indrelid| 1998823
indnatts| 1
indnkeyatts
