Re: ERROR: could not read block 3 in file "base/12511/12270" - Mailing list pgsql-general

From
Subject Re: ERROR: could not read block 3 in file "base/12511/12270"
Date
Msg-id 388256215.3088580.1450926215591.JavaMail.yahoo@mail.yahoo.com
Whole thread Raw
In response to Re: ERROR: could not read block 3 in file "base/12511/12270"  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: ERROR: could not read block 3 in file "base/12511/12270"  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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
defaultuser database.  Maybe I'm being overly picky here but seeing "system" in this context does have a connotation
thatwe 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
databasename will use the O/S user's name which, for administrative tasks, is likely to be "postgres" (you really
shouldn'tuse root for DB-admin stuff) and thus those commands will be able to connect without much, if any, additional
optionssupplied. 
 >
 > Its presence, absence, or modification in now way alters the fundamental operation of PostgreSQL; though its lack
mayfrustrate 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.


pgsql-general by date:

Previous
From:
Date:
Subject: Re: ERROR: could not read block 3 in file "base/12511/12270"
Next
From: Tom Lane
Date:
Subject: Re: ERROR: could not read block 3 in file "base/12511/12270"