Re: fsm and vacuum
От | Michael Shapiro |
---|---|
Тема | Re: fsm and vacuum |
Дата | |
Msg-id | AANLkTi=XOgVm2oUJ2AO4GHE-F3E=3Du0PAh-bZpgyY7H@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: fsm and vacuum (Guillaume Lelarge <guillaume@lelarge.info>) |
Ответы |
Re: fsm and vacuum
("Little, Douglas" <DOUGLAS.LITTLE@orbitz.com>)
Re: fsm and vacuum (Guillaume Lelarge <guillaume@lelarge.info>) |
Список | pgadmin-support |
I understand, but in this case, since the option is offered next to the safe one, most people won't know it isn't safe.<br/>I certainly didn't until I read this posting. I know generally what vacuuming does, but I had no idea that postgresoffered a potentially damaging option. Also, PgAdmin sometimes tells me that a table needs vacuuming, so it is already"advising" people in that area ...<br /><br /><div class="gmail_quote">On Fri, Dec 3, 2010 at 9:19 AM, Guillaume Lelarge<span dir="ltr"><<a href="mailto:guillaume@lelarge.info">guillaume@lelarge.info</a>></span> wrote:<br /><blockquoteclass="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left:1ex;"> Le 03/12/2010 15:17, Michael Shapiro a écrit :<br /> > The document <a href="http://wiki.postgresql.org/wiki/VACUUM_FULL"target="_blank">http://wiki.postgresql.org/wiki/VACUUM_FULL</a> says:<br/> ><br /> > VACUUM FULL, unlike VACUUM, tuples data that has not been deleted, moving it<br /> > into spacesearlier in the file that have been freed. Once it's created a<br /> > free space at the end of the file, it truncatesthe file so that the OS<br /> > knows that space is free and may be reused for other things. Moving in-use<br/> > data around this way has some major downsides and side-effects, especially<br /> > the way VACUUM FULLdoes it. There are better ways to free space if you need<br /> > to and better ways to optimize tables (see below)so *you should essentially<br /> > never use VACUUM FULL*.<br /> ><br /> ><br /> > PgAdmin does not givethe user a comparable warning when it goes to execute<br /> > a VACCUM FULL. Given the potential problems with theFULL option, would it<br /> > make sense for PgAdmin to issue a warning to this effect?<br /> ><br /><br /> I'mnot sure this is the role of pgAdmin to warn people they are doing<br /> potentially stupid things.<br /><font color="#888888"><br/><br /> --<br /> Guillaume<br /> <a href="http://www.postgresql.fr" target="_blank">http://www.postgresql.fr</a><br/> <a href="http://dalibo.com" target="_blank">http://dalibo.com</a><br /></font></blockquote></div><br/>
В списке pgadmin-support по дате отправления: