Re: archive file "00000001000000000000006F" has wrong size: 67118648 instead of 16777216

From: 江川潔 <egawa(at)apteq(dot)jp>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: archive file "00000001000000000000006F" has wrong size: 67118648 instead of 16777216
Date: 2020-11-26 03:06:53
Message-ID: CAH0xBbEiLxGMT9E1y4PpaZJZCoVFBMPFDsth3YZLUeuA30FpgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi
I have corrected it on "restore_command = 'copy
"D:\\BKUP\\pg_archivedir\\PostgreSQL_DEV\\%f" "%p"'".
Thanks,
Kiyoshi

2020年11月25日(水) 19:35 Magnus Hagander <magnus(at)hagander(dot)net>:

> On Wed, Nov 25, 2020 at 3:02 AM 江川潔 <egawa(at)apteq(dot)jp> wrote:
> >
> > Hi,
> >
> > WAL log recovery was failed on wrong log record size. Could you please
> advise me what is wrong in the setting ? Any suggestions will be highly
> appreciated.
> >
> > Thanks,
> > Kiyoshi
> >
> > postgres.conf:
> > wal_level = replica
> > archive_mode = on
> > archive_command = 'copy "%p"
> "D:\\BKUP\\pg_archivedir\\PostgreSQL_DEV\\%f"'
> >
> > recover.conf:
> > restore_command = 'copy "D:\\BKUP\\pg_archivedir\\PostgreSQL_DEV" "%p"'
>
> Does your restore command really not have a %f in it anywhere? That
> definitely seems wrong... But it does seem to copy some files correct,
> which would be weird if it doesn't. Mistake in the report, or is there
> something really weird going on with that PostgreSQL_DEV not being a
> directory but instead some "magic file"?
>
> --
> Magnus Hagander
> Me: https://www.hagander.net/
> Work: https://www.redpill-linpro.com/
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Atul Kumar 2020-11-26 05:53:44 meaning of (to prevent wraparound) ..??
Previous Message Alvaro Herrera 2020-11-26 02:42:44 Re: Potential BRIN Index Corruption