writes:
>>> On 12/23/2015 04:17 PM, Paul Jones wrote:
>>> 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
>>> connotati
> 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 defau
On Wednesday, December 23, 2015 6:45 PM, Tom Lane wrote:
> Paul Jones writes:
> > I have been having disk errors that have corrupted something in
> > my postgres database. Other databases work ok:
>
> > postgres=# SELECT pg_catalog.pg_is_in_recovery();
> > ERROR: could not read block 3
On Wed, Dec 23, 2015 at 5:48 PM, Adrian Klaver
wrote:
> 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:
>>
>> Running on Ubuntu 10.04.
>>
>> paul@kitanglad:~$ psql -U postgres
>> psql
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:
Running on Ubuntu 10.04.
paul@kitanglad:~$ psql -U postgres
psql (9.4.5)
Type "help" for help.
postgres=# SELECT pg_catalog.pg_is_in_recover
Paul Jones writes:
> I have been having disk errors that have corrupted something in
> my postgres database. Other databases work ok:
> postgres=# SELECT pg_catalog.pg_is_in_recovery();
> ERROR: could not read block 3 in file "base/12511/12270": read only 4096 of
> 8192 bytes
Hm. Evidently y
I have been having disk errors that have corrupted something in
my postgres database. Other databases work ok:
Running on Ubuntu 10.04.
paul@kitanglad:~$ psql -U postgres
psql (9.4.5)
Type "help" for help.
postgres=# SELECT pg_catalog.pg_is_in_recovery();
ERROR: could not read block 3 in file
