On 9/25/07, Morris Goldstein <[EMAIL PROTECTED]> wrote:
> On 9/25/07, Scott Marlowe <[EMAIL PROTECTED]> 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 pro
"Morris Goldstein" <[EMAIL PROTECTED]> writes:
> 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.
I don't know that I'd
On 9/25/07, Scott Marlowe <[EMAIL PROTECTED]> 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
On 9/25/07, Morris Goldstein <[EMAIL PROTECTED]> wrote:
> Thanks for your help with pg_resetxlog. It recovered all of our databases,
> and it looks like we got lucky in that no updates were lost.
>
> We are deciding on the goals for our next release, and one of the issues on
> the table is an upgra
Thanks for your help with pg_resetxlog. It recovered all of our databases,
and it looks like we got lucky in that no updates were lost.
We are deciding on the goals for our next release, and one of the issues on
the table is an upgrade to postgres 8. Can you comment on the improvements
in performa
"Morris Goldstein" <[EMAIL PROTECTED]> writes:
> I looked at the pg_resetxlog documentation and have a question. Here
> is output from pg_resetxlog -n:
[ snipped to just the non-constant numbers ]
> Current log file ID: 0
> Next log file segment:1
> Latest checkpo
On 9/22/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Morris Goldstein" <[EMAIL PROTECTED]> writes:
> > ...
> > 2007-09-22 07:06:05 [3060] LOG: could not open file
> > "/var/lib/pgsql/data/pg_xlog/" (log file 0, segment 0): No
> > such file or directory
> > ...
>
> ...
>
> You might
Sorry to reply to myself but here's a bit more info. That strace shows
a crash. The node that was denying logins is now complaining about
checkpoint file 000...000. It appears to be the case that a few
attempts to start converts a db that rejects logins to one that
crashes on startup. (When I first
On 9/22/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Morris Goldstein" <[EMAIL PROTECTED]> writes:
> > Two of the nodes have logs that look like this:
>
> > 2007-09-22 07:06:05 [3060] LOG: could not open file
> > "/var/lib/pgsql/data/pg_xlog/" (log file 0, segment
> > 0): No such fil
"Morris Goldstein" <[EMAIL PROTECTED]> writes:
> Two of the nodes have logs that look like this:
> 2007-09-22 07:06:05 [3060] LOG: could not open file
> "/var/lib/pgsql/data/pg_xlog/" (log file 0, segment
> 0): No such file or directory
> 2007-09-22 07:06:05 [3060] LOG: invalid p
We have a cluster with four nodes, each running a postgres 7.4.8
database. Due to a large amount of pilot error and possibly hardware
problems (still trying to get to the bottom of it all), two of the
databases won't start, and I can't login to two others, with any
registered user.
Two of the node
11 matches
Mail list logo