| From: | "Morris Goldstein" <morris(dot)x(dot)goldstein(at)gmail(dot)com> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Can't connect (2 dbs) or login (2 others) |
| Date: | 2007-09-25 20:17:25 |
| Message-ID: | 41b6f5c20709251317u59c6686eg1ffdb6a58327630e@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/25/07, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>
> But since it hit all of your machines, and at about the same time, I
> tend to think that someone did something to these machines that caused
> this issue, and it's not a 7.4.x problem.
I'm sure it is pilot error, and we're still trying to figure out exactly
which pilot and what error.
Did you update / upgrade kernels, device drivers, hardware, etc...
> What is common between all these systems besides postgresql? Was
> there a power outage? All machines had the same admin one day who had
> a brain cramp and did something stupid?
This occurred as part of an upgrade -- new OS, kernel, drivers.
Simply put, we need more info on how this happened.
>
We've recovered. There is root cause analysis going on. The question is
whether I can use an argument about 8.0 vs. 7.4 reliability from this fiasco
to help us get to 8.0.
8.0 actually is more reliable than 7.4, I assume.
Morris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Madison Kelly | 2007-09-25 20:28:47 | Re: Manually clearing "database "foo" is being accessed by other users" |
| Previous Message | Ralph Smith | 2007-09-25 20:04:02 | pg_restore - invalid file problem |