On Mon, Dec 23, 2013 at 7:48 AM, wrote:
> WARNING: page 1 of relation base/37706/11821 is uninitialized
> CONTEXT: xlog redo vacuum: rel 1663/37706/11821; blk 2, lastBlockVacuumed
> 0
> PANIC: WAL contains references to invalid pages
> CONTEXT: xlog redo vacuum: rel 1663/37706/11821;
After the restart of a PostgreSQL 9.3.1 hot standby doing streaming
replication, the database would not come up again and the logs show
"index contains unexpected zero page at block 0" errors as shown below:
LOG: entering standby mode
LOG: redo starts at 6/55A16990
LOG: consistent reco
Thanks for the reply! Help me please how to use the pg_resetxlog? I read
the documentation
http://www.postgresql.org/docs/8.4/static/app-pgresetxlog.html, but did
not fully understand how to use it. There are many of values...
$ ./pg_resetxlog -n /opt/postgresql/data
pg_control values:
First log
How can I execute rebulding the index, if it does not start and I can't
connect?
On Thu, Nov 15, 2012 at 2:34 AM, VB N wrote:
>
> user=,db= FATAL: index "316879235" contains unexpected zero page at block
>> 264
>> user=,db= HINT: Please REINDEX it.
>>
>> Please tell me what can I do to recover
Dmitriy Tyugaev writes:
> Nov 14 18:24:04 uno postgres84[24208]: [6-1] user=,db= LOG: redo done at
> 237B/90A1DF98
> Nov 14 18:24:04 uno postgres84[24208]: [7-1] user=,db= LOG: last completed
> transaction was at log time 2012-11-10 10:26:28.484922+04
> Nov 14 18:24:04 uno postgres84[24208]: [8-
> user=,db= FATAL: index "316879235" contains unexpected zero page at block
> 264
> user=,db= HINT: Please REINDEX it.
>
> Please tell me what can I do to recover?
>
Did you try re-building the index ? Re-Indexing or re-creating an new index
should resolve this.
Regards,
VBN
Hi list,
After planned rebooting the server dropped the database server PostgreSQL
8.4
When it start the server writes to the log:
Nov 14 18:24:01 uno postgres84[24207]: [1-1] user=,db= LOG: could not bind
IPv6 socket: Cannot assign requested address
Nov 14 18:24:01 uno postgres84[24207]: [1-2]
