Gregory Stark wrote:
> Darren Reed writes:
>
>
>> ERROR: could not read block 1 of relation 1664/0/1233: read only 0 of
>> 8192 bytes
>>
>
> FWIW this is pg_shdepend_reference_index which is actually a bit special. It's
> a "shared" relation which means it spans all your databases. Your
Darren Reed writes:
> For me it has been very reproducible:
If you can put together a self-contained test case that would let
someone else reproduce it, we'd be very interested to take a look.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.
"Peter Woodward" writes:
> creating conversions ... FATAL: could not access file
> "$libdir/ascii_and_mic": No such file or directory
Hm, so did ascii_and_mic.so get installed in your pkglibdir
(ie, /usr/local/lib/postgresql)? If not, where did it end up?
If it is there, what does ldd or local
Darren Reed writes:
> ERROR: could not read block 1 of relation 1664/0/1233: read only 0 of
> 8192 bytes
FWIW this is pg_shdepend_reference_index which is actually a bit special. It's
a "shared" relation which means it spans all your databases. Your reindex
didn't rebuild to. To reindex it yo
As another data point, I upgraded from 8.2.6 to 8.3.6
and I saw those corruption messages after restoring
pg_dump files back into the database with psql and
inserting a bunch of data (some duplicate records
got rejected.) The insertion of new data is via
perl's DBI interface.
This was after the u
The following bug has been logged online:
Bug reference: 4671
Logged by: Peter Woodward
Email address: pe...@petew.org.uk
PostgreSQL version: 8.3
Operating system: FreeBSD 7.0
Description:Cluster Initialisation Fails on FreeBSD
Details:
The following script shows th
