Re: Vacuum, Freeze and Analyze: the big picture

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Vacuum, Freeze and Analyze: the big picture
Date: 2013-06-03 21:26:08
Message-ID: CA+TgmoZ4O76kp=oD_446KzZ4RfSTRik_pp9wJY=VLGJDchHTfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 3, 2013 at 2:56 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Really? I though vacuum held onto its locks until it reached
> vacuum_cost. If it doesn't, then maybe we should adjust the default for
> vacuum_cost_limit upwards.

That would be completely insane.

Or in other words, no, it doesn't do anything like that. :-)

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2013-06-03 21:27:01 Re: Vacuum, Freeze and Analyze: the big picture
Previous Message Kevin Grittner 2013-06-03 20:41:16 Re: Question about storage subsystem of PotgreSQL