On 10/28/14, 3:27 PM, Simon Riggs wrote:
On 28 October 2014 17:50, Jim Nasby <jim.na...@bluetreble.com> wrote:
On 10/28/14, 9:22 AM, Simon Riggs wrote:
2. Some additional code in Autovacuum to rebuild corrupt indexes at
startup, using AV worker processes to perform a REINDEX CONCURRENTLY.
I don't think loading more functionality into autovac is the right way to do
that.
You'd need to explain why and/or suggest your right way.
Why wouldn't we register it as a background worker?
Not only doesn't this have anything to do with vacuum, but it should operate
differently as well: once we've rebuilt everything that needs to be rebuilt the
process should go away until the next startup. That's the opposite of what
autovac does.
The one potential commonality I see is having a launcher process that's
responsible for launching multiple workers (if we want to be rebuilding
multiple indexes at once), but AFAICT that capability is also provided by
bgworker.c.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
