On Mon, Nov 21, 2016 at 11:34 AM, dhaval jaiswal wrote:
> Due to business impact auto vacuum is off.
You have now discovered some of the the negative business impact of
turning it off. If you leave it off, much worse is likely to
follow.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The E
dhaval jaiswal wrote:
> Adding to above. Below are the outputs.
I just meant that you need to ANALYZE all these system catalogs so that
autovacuum can pick up vacuuming them to remove dead tuples. Do not
leave autovacuum turned off anymore.
--
Álvaro Herrerahttps://www.2ndQuadr
(system) table increasing size.
I did check and found it was the bloated size of pg_class which was slowing
down the performance.
It got fixed by adding in routine maintenance task. Things are fine now.
However, I want to know how come pg_class (system table) get bloated/affected.
What could
eneral@postgresql.org
Subject: Re: [GENERAL] pg_class (system) table increasing size.
I did check and found it was the bloated size of pg_class which was slowing
down the performance.
It got fixed by adding in routine maintenance task. Things are fine now.
However, I want to know how come pg
On Mon, Nov 21, 2016 at 10:34 AM, dhaval jaiswal
wrote:
> Due to business impact auto vacuum is off.
>
You won't get much sympathy if you turn this feature off. The question
you should be pondering is how to properly configure it for your
environment.
pg_class gets bloated for the same reas
dhaval jaiswal wrote:
> I did check and found it was the bloated size of pg_class which was slowing
> down the performance.
>
> It got fixed by adding in routine maintenance task. Things are fine now.
Good to know.
> However, I want to know how come pg_class (system table) get
> bloated/affec
eneral@postgresql.org
Subject: Re: [GENERAL] pg_class (system) table increasing size.
On Thu, Nov 17, 2016 at 3:16 PM, Alvaro Herrera
wrote:
> Looks like you lost the stat data awhile ago (probably due to a server
> crash, or pg_stats_reset()) and it never got updated. I suggest doing
> "
On Thu, Nov 17, 2016 at 3:16 PM, Alvaro Herrera
wrote:
> Looks like you lost the stat data awhile ago (probably due to a server
> crash, or pg_stats_reset()) and it never got updated. I suggest doing
> "ANALZYE pg_class" to create initial stats; that might prompt autovacuum
> to vacuum the table
dhaval jaiswal wrote:
> select * from pg_stat_sys_tables where relname = 'pg_class';
>
> -[ RECORD 1 ]---+---
> relid | 1259
> schemaname | pg_catalog
> relname | pg_class
> seq_scan| 1838
> seq_tup_read| 3177416
> idx_scan
pg_class table is of 5 GB. However, the existing row is
> only 2380 only. It's got fragmented.
>
> --
> *From:* Adrian Klaver
> *Sent:* Thursday, November 17, 2016 8:29 PM
> *To:* dhaval jaiswal; David G. Johnston
> *Cc:* pgsql-general@postgresql.
jaiswal; David G. Johnston
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_class (system) table increasing size.
On 11/16/2016 07:08 PM, dhaval jaiswal wrote:
>
>>> Because you are creating (specific) objects.
>
> I have gone through the link and how would i figu
On 11/16/2016 07:08 PM, dhaval jaiswal wrote:
Because you are creating (specific) objects.
I have gone through the link and how would i figure out which
specific object is causing this. Can you please elaborate more here.
We do not have the much temporary table usage.
Since the size is
AM
*To:* dhaval jaiswal
*Cc:* pgsql-general@postgresql.org
*Subject:* Re: [GENERAL] pg_class (system) table increasing size.
On Wed, Nov 16, 2016 at 7:30 PM, dhaval jaiswal mailto:dhava...@hotmail.com>>wrote:
PostgreSQL 9.4.0
Are generalizing here or are you really running 2+ year old
quires maintenance as
well for the pg_class.
It seems its affecting performance.
From: David G. Johnston
Sent: Thursday, November 17, 2016 8:13 AM
To: dhaval jaiswal
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_class (system) table increasing size.
On Wed, Nov 16, 2016 at 7:30 PM, dhaval jaiswal
wrote:
> PostgreSQL 9.4.0
>
Are generalizing here or are you really running 2+ year old patch version?
> Why pg_class table is getting bigger in size.
>
Because you are creating (specific) objects.
See: https://www.postgresql.org/docs/9.6/stat
PostgreSQL 9.4.0
Why pg_class table is getting bigger in size.
How to stop increasing it.
Does it affect the performance.
16 matches
Mail list logo
