From: | <pbj(at)cmicdo(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Paul Jones <pbj(at)cmicdo(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ERROR: could not read block 3 in file "base/12511/12270" |
Date: | 2015-12-24 03:03:35 |
Message-ID: | 388256215.3088580.1450926215591.JavaMail.yahoo@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 12/23/2015 04:17 PM, Paul Jones wrote:
> >
> >I have been having disk errors that have corrupted something in
> >>my postgres database. Other databases work ok:
>
> This isn't the best characterization...the "postgres" data is not a "system" database but rather a convenient default user database. Maybe I'm being overly picky here but seeing "system" in this context does have a connotation that we really don't want to impart onto the "postgres" database.
>
> It is named such because the default user is likewise "postgres" and most utilities when not provided with a database name will use the O/S user's name which, for administrative tasks, is likely to be "postgres" (you really shouldn't use root for DB-admin stuff) and thus those commands will be able to connect without much, if any, additional options supplied.
>
> Its presence, absence, or modification in now way alters the fundamental operation of PostgreSQL; though its lack may frustrate users acclimated to using said defaults.
>
This was one of the big lessons I learned from this. All this time I was
under the mistaken impression that it was special.
> David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-24 05:09:01 | Re: ERROR: could not read block 3 in file "base/12511/12270" |
Previous Message | pbj | 2015-12-24 02:59:00 | Re: ERROR: could not read block 3 in file "base/12511/12270" |