Skip site navigation (1) Skip section navigation (2)

[Fwd: [plans] .plan update]

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Postgresql Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: [Fwd: [plans] .plan update]
Date: 2003-08-31 00:55:59
Message-ID: 1062291359.83670.55.camel@jester (view raw, whole thread or download thread mbox)
Lists: pgsql-advocacy
It would appear that has made a cutover from Sybase to
PostgreSQL in the last 24 hours -- temporarily at least.

Not very high profile, but they do have a fairly high query load.

-----Forwarded Message-----
From: plans(at)nodezero(dot)distributed(dot)net
To: plans(at)lists(dot)distributed(dot)net
Subject: [plans] .plan update
Date: Sun, 31 Aug 2003 00:00:04 +0000

distributed .plan updates in the last 24 hours:

decibel :: 29-Aug-2003 20:09 CDT (Friday) ::

Blower is up and running again; apparently it died because the raid controller
freaked out after a disk failure. I'm still hoping to recover any data that was
modified last night, but if that doesn't happen soon I'll just go with what we

decibel :: 29-Aug-2003 23:58 CDT (Friday) ::

MattR was able to get the database online again, so I now have copies of the 3
tables. This means that no data should end up lost out of all of this.

There are 3 options we have right now. First, we can attempt to repair the
existing stats database. MattR's attempting this right now. The second option
is to drop the existing database, restore from the July 12th backup, and bring
in the updated information. The third option is for us to cut-over to stats
running on PostgreSQL, which is 95% done right now.

I'm playing it a bit by ear before deciding which way to go. Going to
PostgreSQL is very tempting, since we'll need to do it in the near future
anyway, but I don't like the idea of going to production when it's not complete
and hasn't been beta-tested.

Whatever happens, stats definitely won't be up until tomorrow afternoon at the
very earliest.

decibel :: 30-Aug-2003 00:03 CDT (Saturday) ::

I just talked with MattR; he's not going to be able to recover the existing
database. We'll be restoring from a backup as soon as it's done bunzipping.

decibel :: 30-Aug-2003 13:21 CDT (Saturday) ::

Quick update...

Sybase is up and running again, but with month-old data. Sybase's BCP routine
doesn't handle embedded delimiter characters very well, so I'm a bit uneasy
about trusting the data pulled out of the corrupted database, especially for
loading in a month of changes impacting 2600 participants.

Because of this, I'm concentrating on getting the data loaded into PostgreSQL,
since there should be very few changes (the data is PostgreSQL is only a few
hours older than when I shut down stats).

In any case, progress is being made and we're much closer to working stats now
than we were yesterday.

decibel :: 30-Aug-2003 18:04 CDT (Saturday) ::

The PostgreSQL copy of stats is up-to-date now, although it does need to
process August. The HTML side still needs to be setup, which paul will work on
in 10 hours or so (it's midnight his time right now).

Unfortunately this means another day without stats, but I'm really
uncomfortable with trying to get data back into Sybase properly. There might
be some information that has been lost going into PostgreSQL, but it should
only be some changes that were made in a window of about 8 hours. The Sybase
database is currently 6 weeks out of date, so there's much more room for

While paul is getting the HTML stuff setup there might be periods where you can
not get to any stats web pages at all. Don't worry, this is just him working on

I want to thank everyone for their patience; the end is in sight.

plans mailing list


pgsql-advocacy by date

Next:From: Marc G. FournierDate: 2003-08-31 02:14:32
Subject: Re: [Fwd: [plans] .plan update]
Previous:From: Ian BarwickDate: 2003-08-30 20:21:23
Subject: Re: PostgreSQL now has a section on the Database Journal website

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group