On Thu, Jul 31, 2003 at 01:41:54PM -0400, [EMAIL PROTECTED] wrote:
>
> well, i was close. i didn't realize that i had to do a (non-full)
> vacuum to mark deleted space as free.
Ooops, I think I was still unclear. VACUUM FULL actually re-arranges
the file, and returns it to the filesystem. Plain
On Thu, 31 Jul 2003, Andrew Sullivan wrote:
> On Thu, Jul 31, 2003 at 08:51:09AM -0400, [EMAIL PROTECTED] wrote:
> >
> > well, i can admit that i am confused. my assumption is that when a row
> > is deleted in pg, that row is merely marked as 'gone' until a vacuum-full
> > is done. my further ass
On Thu, Jul 31, 2003 at 08:51:09AM -0400, [EMAIL PROTECTED] wrote:
>
> well, i can admit that i am confused. my assumption is that when a row
> is deleted in pg, that row is merely marked as 'gone' until a vacuum-full
> is done. my further assumption is that if i continue to add rows, those
> rows
On Thu, 31 Jul 2003, Peter Eisentraut wrote:N
> [EMAIL PROTECTED] writes:N
> > sorry, when i referred to "disk space used" i meant the actual amount
> > used by live rows. if i insert 1000 rows then delete 999 of them, the
> > disk file will be the size of the 100 row container (make that 1000, no
[EMAIL PROTECTED] writes:
> sorry, when i referred to "disk space used" i meant the actual amount
> used by live rows. if i insert 1000 rows then delete 999 of them, the
> disk file will be the size of the 100 row container (make that 1000, not
> 100 - i cannot backspace here) until i do a "vacuum
sorry, when i referred to "disk space used" i meant the actual
amount used by live rows. if i insert 1000 rows then delete
999 of them, the disk file will be the size of the 100 row
container (make that 1000, not 100 - i cannot backspace here)
until i do a "vacuum full" - which does a table lock, w
<[EMAIL PROTECTED]> writes:
> i've been browsing the documentation online, and i can't
> find where the storage layouts for tables and indexes are
> explained.
>
> i'd like to be able to figure out, given a table or two
> with a simple schema (no ineritance) and some indexes, and
> a number of row
i've been browsing the documentation online, and i can't
find where the storage layouts for tables and indexes are
explained.
i'd like to be able to figure out, given a table or two
with a simple schema (no ineritance) and some indexes, and
a number of rows currently in these tables, how much disk
