From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Add pages deleted from pending list to FSM |
Date: | 2015-09-18 13:27:49 |
Message-ID: | 11156.1442582869@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
[ moving thread to -hackers ]
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> So autoanalyze still doesn't call IndexFreeSpaceMapVacuum().
> That is, only backend can clean the list in INSERT-only workload.
> I don't think that this is desirable. Because the backend will
> periodically take a big performance penalty.
> So I'm thinking that even autoanalyze should call IndexFreeSpaceMapVacuum()
> to clean the list in a background, in order to avoid such spikes in
> INSERT response time. Thought?
It seems quite bizarre for auto-analyze to do that. auto-vacuum, sure,
but I do not think this should get plugged into ANALYZE.
Maybe we need to rethink the rules for what is autovacuum vs. autoanalyze,
or come up with some third thing that the autovac daemon does for indexes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2015-09-18 14:16:33 | Re: [COMMITTERS] pgsql: Add pages deleted from pending list to FSM |
Previous Message | Teodor Sigaev | 2015-09-18 11:33:19 | Re: pgsql: Fix oversight in tsearch type check |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-09-18 13:32:16 | Re: row_security GUC, BYPASSRLS |
Previous Message | Adam Brightwell | 2015-09-18 13:01:15 | Re: row_security GUC, BYPASSRLS |