On Mon, Oct 24, 2011 at 10:25 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
On 24-10-2011 10:57, Robert Haas wrote:
I think the main reason why vacuumlo is a contrib module rather than
in core is that it is just a heuristic, and it might not be what
everyone wants to do. You could
Euler Taveira de Oliveira eu...@timbira.com writes:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it.
I'm not terribly thrilled with that because (a) large objects seem
On Mon, Oct 24, 2011 at 12:56 AM, Euler Taveira de Oliveira
eu...@timbira.com wrote:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it. While dealing with large objects
On 24-10-2011 10:57, Robert Haas wrote:
I think the main reason why vacuumlo is a contrib module rather than
in core is that it is just a heuristic, and it might not be what
everyone wants to do. You could store a bunch of large objects in the
database and use the returned OIDs to generate
On 24-10-2011 11:36, Tom Lane wrote:
Euler Taveira de Oliveiraeu...@timbira.com writes:
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it.
I'm not terribly thrilled with
Hi,
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it. While dealing with large objects (LO), we have lo
contrib module that helps with LO maintenance but has some
