Hi,
Since the autovacuum decides whether to vacuum or analyze a table based on
thresholds .As the threshold to trigger autovacuum is high so it might not have
been triggered .
vacuum_trigger_threshold =
autovacuum_vacuum_threshold + (autovacuum_vacuum_scale_factor × n_live_tup)
You may check b
On Fri, Oct 17, 2025 at 09:01:52AM +0200, Laurenz Albe wrote:
> On Fri, 2025-10-17 at 00:49 -0400, Ron Johnson wrote:
> > On Thu, Oct 16, 2025 at 6:05 PM Greg Sabino Mullane
> > wrote:
> > >
> > > TDE, on the other hand, is a very complex and difficult thing to add into
> > > Postgres.
> >
> >
On Thu, Oct 30, 2025 at 2:41 PM Dimitrios Apostolou wrote:
> On Thursday 2025-10-30 18:00, Ron Johnson wrote:
>
> >On Thu, Oct 30, 2025 at 11:55 AM Dimitrios Apostolou
> wrote:
>
> > > SELECT name,setting FROM pg_settings WHERE name ILIKE '%factor%' ;
> >name
On Thursday 2025-10-30 18:00, Ron Johnson wrote:
On Thu, Oct 30, 2025 at 11:55 AM Dimitrios Apostolou wrote:
> SELECT name,setting FROM pg_settings WHERE name ILIKE '%factor%' ;
name | setting
---+-
On Thu, Oct 30, 2025 at 11:55 AM Dimitrios Apostolou wrote:
> Hello list,
>
> I have a table that is constantly growing, and it's not being
> vacuumed/analyzed. I think my problem is rather common, but how to even
> debug it if "nothing works"?
>
> I've already set log_autovacuum_min_duration = 0
On 10/30/25 08:22, Rumpi Gravenstein wrote:
I've seen two indexes created on the same table/column when you create a
primary key as part of table create ddl and then also run a separate
create index statement for the same table/column.
Yes it is possible to create two indexes on a given table
Hello list,
I have a table that is constantly growing, and it's not being
vacuumed/analyzed. I think my problem is rather common, but how to even
debug it if "nothing works"?
I've already set log_autovacuum_min_duration = 0 but the table is never
mentioned in my logs, grep'ing for "vacuum".
I've seen two indexes created on the same table/column when you create a
primary key as part of table create ddl and then also run a separate create
index statement for the same table/column.
On Thu, Oct 30, 2025 at 10:42 AM Adrian Klaver
wrote:
> On 10/30/25 01:55, Colin 't Hart wrote:
> >
On 10/30/25 01:55, Colin 't Hart wrote:
relname | relnamespace | relpersistence
--+--+o
|524799410 | p
|524799410 | p
(2 rows)
Well so much for that guess. I was exploring the idea that the sequence
may hav
relname | relnamespace | relpersistence
--+--+
|524799410 | p
|524799410 | p
(2 rows)
On Wed, 29 Oct 2025 at 17:28, Adrian Klaver wrote:
>
> On 10/29/25 06:40, Colin 't Hart wrote:
> > As expected the dump contain
10 matches
Mail list logo
