Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-07-10 Thread Alvaro Herrera
Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > I think we could give autovac a "reason for being started", which would > > normally be the periodic stuff, but if the postmaster got the signal > > from a backend, pass that info to autovac and it could use a different > > database s

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-29 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > I think we could give autovac a "reason for being started", which would > normally be the periodic stuff, but if the postmaster got the signal > from a backend, pass that info to autovac and it could use a different > database selection algorithm -- say,

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-29 Thread Tom Lane
"Jim C. Nasby" <[EMAIL PROTECTED]> writes: > I think it'd be good to put a big, fat WARNING in the log if we fire up > an autovac to avoid an XID wrap, since it's an indication that the > vacuuming scheme that's in place probably isn't good enough. No, for nonconnectable databases it'd be expected

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-29 Thread Jim C. Nasby
On Thu, Jun 29, 2006 at 09:39:27AM +0100, Simon Riggs wrote: > On Wed, 2006-06-28 at 20:08 -0400, Tom Lane wrote: > > In fact, maybe we should just force an autovac cycle for any DB that > > appears to be approaching wraparound, rather than waiting for the > > shutdown-before-wraparound code to kic

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-29 Thread Alvaro Herrera
Tom Lane wrote: > In fact, maybe we should just force an autovac cycle for any DB that > appears to be approaching wraparound, rather than waiting for the > shutdown-before-wraparound code to kick in. Getting into that state > amounts to whacking DBAs upside the head for being stupid, which > doe

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-29 Thread Simon Riggs
On Wed, 2006-06-28 at 20:08 -0400, Tom Lane wrote: > In fact, maybe we should just force an autovac cycle for any DB that > appears to be approaching wraparound, rather than waiting for the > shutdown-before-wraparound code to kick in. Getting into that state > amounts to whacking DBAs upside the

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-28 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > This patch has the nasty side effect mentioned above -- people will have > to set template0 as connectable and manually run vacuum on it > periodically, unless they run autovacuum. That's pretty messy --- making template0 connectable is a great way to s

Re: [PATCHES] [HACKERS] Non-transactional pg_class, try 2

2006-06-28 Thread Alvaro Herrera
Alvaro Herrera wrote: > Tom Lane wrote: > > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > > What I'm after is not freezing for read-only media, nor archive, nor > > > read-only tables. What I'm after is removing the requirement that all > > > databases must be vacuumed wholly every 2 billion tran