pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #5261: Invalide page header
3+ messages / 3 participants
[nested] [flat]
* BUG #5261: Invalide page header
@ 2010-01-04 13:44 Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>
0 siblings, 1 reply; 3+ messages in thread
From: Takesver Kumar Thakur @ 2010-01-04 13:44 UTC (permalink / raw)
To: pgsql-bugs
The following bug has been logged online:
Bug reference: 5261
Logged by: Takesver Kumar Thakur
Email address: takesver.thakur@mobilefundas.com
PostgreSQL version: postgresql-8.1
Operating system: centos 5
Description: Invalide page header
Details:
Hi ,
I received warning on my postgres db,when I fire query,so please provide me
any possible solution.
WARNING: invalid page header in block 32129 of relation "cdr"; zeroing out
page
Regards,
T K Thakur
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #5261: Invalide page header
@ 2010-01-04 19:28 Robert Haas <robertmhaas@gmail.com>
parent: Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>
0 siblings, 0 replies; 3+ messages in thread
From: Robert Haas @ 2010-01-04 19:28 UTC (permalink / raw)
To: Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>; +Cc: pgsql-bugs
On Mon, Jan 4, 2010 at 8:44 AM, Takesver Kumar Thakur
<takesver.thakur@mobilefundas.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5261
> Logged by: Takesver Kumar Thakur
> Email address: takesver.thakur@mobilefundas.com
> PostgreSQL version: postgresql-8.1
> Operating system: centos 5
> Description: Invalide page header
> Details:
>
> Hi ,
>
> I received warning on my postgres db,when I fire query,so please provide me
> any possible solution.
>
> WARNING: invalid page header in block 32129 of relation "cdr"; zeroing out
> page
I suspect that this is caused by one of two things:
1. You haven't specified which minor version of PostgreSQL 8.1 you are
running, but if it's not the latest one (8.1.19) you should upgrade.
There may be data corruption bugs that have been fixed in newer
versions. I would suggest a dump and reload cycle to make sure you've
got a clean install, if that's practical.
- or -
2. Your hardware is busted.
...Robert
^ permalink raw reply [nested|flat] 3+ messages in thread
* BUG #18069: pg_is_in_recovery() is false but recovery is not yet completed(i.e. recovery.signal is present)
@ 2023-08-25 06:40 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 3+ messages in thread
From: PG Bug reporting form @ 2023-08-25 06:40 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: sahul02@gmail.com
The following bug has been logged on the website:
Bug reference: 18069
Logged by: AK
Email address: sahul02@gmail.com
PostgreSQL version: 15.2
Operating system: Debian Ubuntu
Description:
created a backup_label and tablespace_map file
-rw-r--r-- 1 postgres postgres 34 Aug 24 15:27 tablespace_map
-rw-r--r-- 1 postgres postgres 0 Aug 24 15:27 recovery.signal
-rw-r--r-- 1 postgres postgres 205 Aug 24 15:27 backup_label
Contents of the files are:
backup-label:
----------------
START WAL LOCATION: 0/6000028 (file 000000010000000000000006)
CHECKPOINT LOCATION: 0/6000060
BACKUP METHOD: streamed
BACKUP FROM: primary
START TIME: 2023-08-24 14:09:58 IST
LABEL: label
START TIMELINE: 1
tablespace_map
----------------------
16384 /pgsql/pg15_edb/tsdata/data
postgres log says ....
2023-08-24 15:25:13 IST LOG: database system was interrupted; last known up
at 2023-08-24 14:09:58 IST
2023-08-24 15:25:13 IST LOG: database system was not properly shut down;
automatic recovery in progress
2023-08-24 15:25:13 IST LOG: redo starts at 0/6000028
2023-08-24 15:25:13 IST LOG: invalid record length at 0/6000110: wanted 24,
got 0
2023-08-24 15:25:13 IST LOG: redo done at 0/60000D8 system usage: CPU:
user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2023-08-24 15:25:13 IST LOG: checkpoint starting: end-of-recovery immediate
wait
2023-08-24 15:25:13 IST LOG: checkpoint complete: wrote 3 buffers (0.0%); 0
WAL file(s) added, 0 removed, 0 recycled; write=0.007 s, sync=0.002 s,
total=0.027 s; sync files=2, longest=0.002 s, average=0.001 s; distance=0
kB, estimate=0 kB
2023-08-24 15:25:13 IST LOG: database system is ready to accept
connections
but the recovery.signal is present still. and backup_label and
tablespace_map file has not renamed yet to backup_label.old and
tablespace_map.old.
Actually i have scipt which basically create backup_label and tablespace_map
file under the source data directory and try to run recovery using PITR.
My script log says:
Thu 24 Aug 2023 03:27:19 PM IST :: Checking recovery status... 1
Thu 24 Aug 2023 03:27:19 PM IST :: Recovery status: i.e. psql -t -c "SELECT
pg_is_in_recovery() is f.
Thu 24 Aug 2023 03:27:19 PM IST :: Recovery complete
the timing is 15:27:19PM .. but the log timing is around 15.25:13 ...lag of
2 minutes.
Question is why the recovery.log file is still present and the
backup_label.old and tablespace_map.old not available if the recovery is
already completed.i.e. psql -t -c "SELECT pg_is_in_recovery() output is f .
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-08-25 06:40 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-01-04 13:44 BUG #5261: Invalide page header Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>
2010-01-04 19:28 ` Robert Haas <robertmhaas@gmail.com>
2023-08-25 06:40 BUG #18069: pg_is_in_recovery() is false but recovery is not yet completed(i.e. recovery.signal is present) PG Bug reporting form <noreply@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox