From: | "mac_man2005(at)hotmail(dot)it" <mac_man2005(at)hotmail(dot)it> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: About tapes |
Date: | 2010-06-21 00:39:03 |
Message-ID: | BLU0-SMTP71314FEA77C360F9446065E6C30@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert, so in my example:
- tapes are stored in different files (one tape per file)
- you confirm those first blocks are garbage
- you confirm they could be rewritten with new data
This means that we can do recycle space using one tape per file. Correct?
So, in this case, why do we need to use logical tapesets?
In other words, why Tom affirmed it was impossible to recycle space
implementing one tape per file?
Il 20/06/2010 23:20, Robert Haas ha scritto:
> On Sat, Jun 19, 2010 at 4:57 AM, mac_man2005(at)hotmail(dot)it
> <mac_man2005(at)hotmail(dot)it> wrote:
>
>> Tom, Robert,
>> thank you.
>>
>> Now it is clearer how space on tapes is recycled.
>>
>> I tried to follow Robert's example but storing one tape per separate file.
>> Read in the first block of each run (hosted by separate tapes and so by
>> separate files) and output them into extra storage, wherever this extra
>> storage is.
>> Again, those first input blocks are now garbage: is it correct?
>>
> Yes.
>
>
>> In this case, what happens when trying to recycle those garbage blocks by
>> hosting the result of merging the second block of each run?
>>
> You just overwrite them with the new data.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-06-21 01:31:34 | Re: beta3 & the open items list |
Previous Message | Florian Pflug | 2010-06-20 23:42:00 | Re: beta3 & the open items list |