Re: vacuum visibility relevance

2023-12-03 Thread David Rowley
On Mon, 4 Dec 2023 at 15:08, senor wrote: > PG version 11.4 You're missing out on over 3 years of bug fixes running that version. I see you're planning an upgrade to v15. You should update to 11.22 in the meantime. That's the latest and final version of v11. > If I start a vacuum on this table w

Re: vacuum visibility relevance

2023-12-03 Thread Laurenz Albe
On Mon, 2023-12-04 at 02:08 +, senor wrote: > Simplified Scenario: > 40+ gig table with 20+ indexes receiving log event type records in an append > only fashion. Log tables typically receive tons of INSERTs. Over twenty indexes are too many. > One of the columns is a sequence ID. > PG versi

Re: vacuum visibility relevance

2023-12-03 Thread Ron Johnson
On Sun, Dec 3, 2023 at 9:08 PM senor wrote: > Hi All, > > Simplified Scenario: > 40+ gig table with 20+ indexes receiving log event type records in an > append only fashion. > One of the columns is a sequence ID. > PG version 11.4 > > If I start a vacuum on this table when sequence ID is 1 millio

vacuum visibility relevance

2023-12-03 Thread senor
Hi All, Simplified Scenario: 40+ gig table with 20+ indexes receiving log event type records in an append only fashion. One of the columns is a sequence ID. PG version 11.4 If I start a vacuum on this table when sequence ID is 1 million, and the table continues to accumulate new events, when va