Re: Idea for getting rid of VACUUM FREEZE on cold pages
От | Robert Haas |
---|---|
Тема | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
Дата | |
Msg-id | AANLkTimy4hDyTqbrsi2XIXDklRRJkcA55myaxL5EZrAc@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Idea for getting rid of VACUUM FREEZE on cold pages ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: Idea for getting rid of VACUUM FREEZE on cold
pages
Re: Idea for getting rid of VACUUM FREEZE on cold pages |
Список | pgsql-hackers |
On Thu, May 27, 2010 at 3:15 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > Jesper Krogh <jesper@krogh.cc> wrote: > >> Couldn't pages that are totally filled by the same transaction, be > >> frozen on the initial write? > > As far as I'm aware, that can only be done if: > > (a) The tuples were written within the same transaction which > created or truncated the table. > > *or* > > (b) The writing transaction and all transactions concurrent to it > have completed by the time the page is about to be written. Actually, I think this is true only in case (b). In case (a), you mess up visibility with respect to other command-IDs within the transaction. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: