CVS corruption/mistagging?
in [PgSql]
|
Prev: Bug: Buffer cache is not scan resistant
Next: CREATE DATABASE cannot be executed from a function or multi-command string
From: Magnus Hagander on 15 Aug 2007 03:18 Tom Lane wrote: > Magnus Hagander <magnus(a)hagander.net> writes: >> Tom Lane wrote: >>> Good, but the salient followup questions to that are (1) backed up to >>> where exactly?, and (2) how many days' past backups could we get at, >>> if we had to? > >> They are dumped to a NFS share on this schedule. That NFS share is >> dumped to tape by systems at Conova - I'll let Stefan fill in the >> details about that. > > That's good as far as it goes, but seeing that PG is a worldwide > organization now, I wonder whether our primary CVS shouldn't have > backups on several continents. Pardon my paranoia ... but our > collective arses have been saved by offsite backups at least once > already ... The CVS repository is already synced almost-live back to both svr1 in panama and the anoncvs box in the US. It will be synced to the new VM marc is setting up as well. I assume these machines also have some kind of backup - Marc will have to fill in on that. Oh, and the plan is to have the entire VM synced up between austria and panama machine once / day again once Marc has fixed the issues with that box. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo(a)postgresql.org so that your message can get through to the mailing list cleanly
From: Alvaro Herrera on 15 Aug 2007 03:24 Tom Lane wrote: > Magnus Hagander <magnus(a)hagander.net> writes: > > Tom Lane wrote: > >> Good, but the salient followup questions to that are (1) backed up to > >> where exactly?, and (2) how many days' past backups could we get at, > >> if we had to? > > > They are dumped to a NFS share on this schedule. That NFS share is > > dumped to tape by systems at Conova - I'll let Stefan fill in the > > details about that. > > That's good as far as it goes, but seeing that PG is a worldwide > organization now, I wonder whether our primary CVS shouldn't have > backups on several continents. Pardon my paranoia ... but our > collective arses have been saved by offsite backups at least once > already ... We already have that -- there's plenty of people who have rsync'ed copies of the repository. Now, I don't back it up, so if someone makes a mistake my copy will faithfully follow it. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
From: "Marko Kreen" on 15 Aug 2007 03:33 On 8/15/07, Tom Lane <tgl(a)sss.pgh.pa.us> wrote: > I wrote: > > Kris Jurka <books(a)ejurka.com> writes: > >> It looks like parts of the CVS repository have been mistagged as belonging > >> to REL7_4_STABLE or have been corrupted somehow: > I have no idea how you make CVS do that, but I'm > sure there is some magic one-liner for it. Something like "cvs tag" without -F on the HEAD? -- marko ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
From: Stefan Kaltenbrunner on 15 Aug 2007 04:38 Magnus Hagander wrote: > Tom Lane wrote: >> Magnus Hagander <magnus(a)hagander.net> writes: >>> Tom Lane wrote: >>>> Good, but the salient followup questions to that are (1) backed up to >>>> where exactly?, and (2) how many days' past backups could we get at, >>>> if we had to? >>> They are dumped to a NFS share on this schedule. That NFS share is >>> dumped to tape by systems at Conova - I'll let Stefan fill in the >>> details about that. >> That's good as far as it goes, but seeing that PG is a worldwide >> organization now, I wonder whether our primary CVS shouldn't have >> backups on several continents. Pardon my paranoia ... but our >> collective arses have been saved by offsite backups at least once >> already ... > > The CVS repository is already synced almost-live back to both svr1 in > panama and the anoncvs box in the US. It will be synced to the new VM > marc is setting up as well. I assume these machines also have some kind > of backup - Marc will have to fill in on that. > > Oh, and the plan is to have the entire VM synced up between austria and > panama machine once / day again once Marc has fixed the issues with that > box. yeah that has been my understanding as well though I'm not sure if marc has set up the sync of the full VM already. Stefan ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
From: Stefan Kaltenbrunner on 15 Aug 2007 04:41
Magnus Hagander wrote: > Tom Lane wrote: >> Magnus Hagander <magnus(a)hagander.net> writes: >>> Tom Lane wrote: >>>> I'd like someone to double-check that though. Also maybe we should back >>>> up the repository first? >>> Just for your info: all VMs on tribble, which includes cvs, are backed >>> up at 02:30 every day, CEST >> Good, but the salient followup questions to that are (1) backed up to >> where exactly?, and (2) how many days' past backups could we get at, >> if we had to? > > 1) The entire VM, with "dump" > 2) We have today, yesterday and one weekly (copies the daily on monday, > if I read it right) > > They are dumped to a NFS share on this schedule. That NFS share is > dumped to tape by systems at Conova - I'll let Stefan fill in the > details about that. that's exactly what happens on the backup side here - but maybe I missed an earlier mail - is something broken on tribble or on the new CVS VM that requires a restore from backup ? Stefan ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo(a)postgresql.org so that your message can get through to the mailing list cleanly |