Re: Table size is constantly growing and causing performance problems

[srinivasan s <srinioracledba7@xxxxxxxxx>]

What is the functional difference between regular autovaccum and autovaccum (to prevent wrap around) 

On Wed, 12 Feb, 2025, 8:45 pm Mahesh Shetty, <maheshetty20@xxxxxxxxx> wrote:

Yes - The tuples are inserted into the heap and checked if they are valid as per the constraint. If it fails, it’s marked as deleted.

regards, 

Mahesh Shetty

On Wed, Feb 12, 2025 at 1:53 PM srinivasan s <srinioracledba7@xxxxxxxxx> wrote:

Searched yesterday's log, there were 2000+ unique constraints error. I don't know if it is the contributor

On Wed, 12 Feb, 2025, 1:42 pm srinivasan s, <srinioracledba7@xxxxxxxxx> wrote:

Hi Mahesh, I see unique constraint violation errors on the logs, is this anyway related to the issue that I explained?

On Wed, Feb 12, 2025 at 1:23 PM Mahesh Shetty <maheshetty20@xxxxxxxxx> wrote:

Do you see "duplicate key violations" in the logs ?

Regards,

Mahesh Shetty

On Wed, 12 Feb 2025 at 13:13, srinivasan s <srinioracledba7@xxxxxxxxx> wrote:

Hi Shammat,

There were some very old idle sessions waiting for clientread, which we have killed. no idle in transaction for a long time

On Wed, Feb 12, 2025 at 1:08 PM <shammat@xxxxxxx> wrote:

srinivasan s schrieb am 12.02.2025 um 05:44:
> One of the tables in our database suddenly started  growing very
> fast without any changes to the environment. it has grown over 10GB
> in the last week and this is causing performance issues. We ended up
> adding an index to solve the performance problem but the table
> growth didn't stop. It is growing continuously. we are using
> postgres version 12 on ubuntu
>
> 3. Also noticed that there is a auto vacuum job running on the table with (to prevent wraparound)

Do you have any connections with the state "idle in transaction"? They would prevent (auto) vacuum.