Re: Vacuum problem
| От | S H |
|---|---|
| Тема | Re: Vacuum problem |
| Дата | |
| Msg-id | BAY155-W40A7B02A7180456D53D529FDA10@phx.gbl обсуждение исходный текст |
| Ответ на | Re: Vacuum problem (Scott Marlowe <scott.marlowe@gmail.com>) |
| Ответы |
Re: Vacuum problem
|
| Список | pgsql-general |
I am doing regular insertion/deletion on the same tables .. and running vacuum in an hour...
I suspect there is bloating in my tables.. but how does bloating in pgcatalog is happening is not clear...
> Normally vacuum full is NOT required on a regular basis. However, if> you did something like creation 100M tables and then dropped them, or
> did it one at a time real fast, you could outrun your autovacuum
> daemons and get bloat in the pg catalog tables.
>
> Just offering a possibility for why a connection might be taking a
> long time. There's plenty of other possibilities I'm sure.
> did it one at a time real fast, you could outrun your autovacuum
> daemons and get bloat in the pg catalog tables.
>
> Just offering a possibility for why a connection might be taking a
> long time. There's plenty of other possibilities I'm sure.
В списке pgsql-general по дате отправления: