launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04064
Re: Archive deletion strategy
On Tue, 3 Aug 2010 11:08:03 +0100, Julian Edwards <julian.edwards@xxxxxxxxxxxxx> wrote:
> > What actions do we have?
> > ------------------------
> >
> > As I see it we currently have the following:
> >
> > 1. Move creation of DELETED publishing records to the publisher.
>
> We don't need to do that at all because we're going to delete those rows
> entirely.
>
> > 2. Modify the publisher to remove COPY archives from disk as well as
> > PPAs.
> > 3. Modify the publisher to also remove the librarian files of COPY
> > archives. (Alternatively we could extend the garbage collection
> > approach used for PPAs to COPY archives.)
>
> You don't need to do this at all, the GC will DTRT for unreferenced files. We
> just need to make sure we only delete the SPRF/BPF rows if there's no more
> publications referencing them.
>
> > 4. Modify the publisher to delete db rows of publication records,
> > unique sources and binaries, etc. in COPY archies. (Less important
> > than deleteting the librarian files.)
> >
> > There will be alternative or further actions depending on what we want
> > to achieve.
>
> I think that's pretty much it, although we need to examine exactly which
> database rows need to be deleted and under what conditions. I've added some
> ON DELETE CASCADEs in the past where it's a no brainer but it won't delete
> everything because of the multiple publication referencing package files
> issue.
Just to be clear, you are advocating deleting every trace of an archive
(except records referenced elsewhere), as soon as the publisher runs
after you delete an archive, for all archive types?
Thanks,
James
Follow ups
References