RE: reloption to prevent VACUUM from truncating empty pages at theend of relation
| От | Tsunakawa, Takayuki |
|---|---|
| Тема | RE: reloption to prevent VACUUM from truncating empty pages at theend of relation |
| Дата | |
| Msg-id | 0A3221C70F24FB45833433255569204D1FBBA486@G01JPEXMBYT05 обсуждение исходный текст |
| Ответ на | Re: reloption to prevent VACUUM from truncating empty pages at theend of relation (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: reloption to prevent VACUUM from truncating empty pages at theend of relation
|
| Список | pgsql-hackers |
From: Robert Haas [mailto:robertmhaas@gmail.com] > I don't think that a VACUUM option would be out of place, but a GUC > sounds like an attractive nuisance to me. It will encourage people to > just flip it blindly instead of considering the particular cases where > they need that behavior, and I think chances are good that most people > who do that will end up being sad. Ouch, I sent my previous mail before reading this. I can understand it may be cumbersome to identify and specify each table,so I tend to agree the parameter in postgresql, which is USERSET to allow ALTER DATABASE/USER SET to tune specificdatabases and applications. But should the vacuuming of system catalogs also follow this setting? Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: