Re: [ADMIN] Vacuum explained

2003-01-07 Thread Tom Lane
Tilo Schwarz <[EMAIL PROTECTED]> writes: > Do you try to reuse tuples with a similar storage size (or something like > that) No. If we try to put a tuple on a page, and there's room there, we'll store it. There is no intra-page fragmentation problem because we can always reshuffle the tuples on

Re: [ADMIN] Vacuum explained

2003-01-07 Thread Tilo Schwarz
Tom Lane writes: > > Unused = # of tuples awaiting being reused > > These are not actually tuples, but tuple slots (page item pointers) > that are open for re-use. Maybe this is a good place to ask this: How do you actually reuse a tuple (or the space the tuple needed on disk) if the number of b

Re: [ADMIN] Vacuum explained -> Dangerous ?

2003-01-07 Thread Tom Lane
"Gaetano Mendola" <[EMAIL PROTECTED]> writes: > This mean that if a process do a "begin transaction" and stay there one > month without > activity all row delete or updated after that "begin transaction" remain > there for ever ? Actually not, because the transaction does not start internally (MyP

Re: [ADMIN] Vacuum explained -> Dangerous ?

2003-01-07 Thread Gaetano Mendola
"Tom Lane" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Robert Treat <[EMAIL PROTECTED]> writes: > > Tup = # of "rows" in your table > > Right. This is the number of rows remaining after the vacuum, to be > precise. > > > Keep = # of tuples that the db did no

Re: [ADMIN] Vacuum explained

2003-01-06 Thread Tom Lane
Robert Treat <[EMAIL PROTECTED]> writes: > Tup = # of "rows" in your table Right. This is the number of rows remaining after the vacuum, to be precise. > Keep = # of tuples that the db did not feel it could safely mark/remove > (probably envolved in some type of transaction) More specifically,

Re: [ADMIN] Vacuum explained

2003-01-06 Thread Robert Treat
This is a rough description, should anyone see a need to correct it please do so. On Sat, 2003-01-04 at 09:42, Gaetano Mendola wrote: > NOTICE: Pages 2518: Changed 38, Empty 0; Tup 75489: Vac 447, Keep 68661, > UnUsed 144574. > Total CPU 1.31s/0.25u sec elapsed 48.23 sec. Pages = the # o

[ADMIN] Vacuum explained

2003-01-04 Thread Gaetano Mendola
Hi all, again me on this argument. Can some one explain the messages obtained during a vacuum? For example this is a part ( in the attachment you'll find the entire log ) of what I obtain during the vacuum, now I do on my production DB a vacuum each 60 minutes, before was twice in a Day. NOTICE: