| From: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PG13 pg_receivewal failing |
| Date: | 2020-09-25 08:16:28 |
| Message-ID: | 6972d399-09f9-b00e-7702-28cdd2a0b299@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 9/25/20 3:46 AM, Fujii Masao wrote:
>
>
> On 2020/09/25 5:51, Grigory Smolkin wrote:
>> Hello!
>>
>> I`ve encountered the following error when trying to stream WAL via
>> pg_receivewal:
>>
>> pg_receivewal -p 11770 --synchronous -D /wal/node -v
>> pg_receivewal: starting log streaming at 0/1000000 (timeline 1)
>> pg_receivewal: error: unexpected termination of replication stream:
>> ERROR: requested WAL segment 000000010000000000000001 has already
>> been removed
>> pg_receivewal: disconnected; waiting 5 seconds to try again
>>
>>
>> Is there something awry with start position calculation, or am I
>> doing something wrong?
>
> I guess that 000000010000000000000001.partial file remained in /wal/node
> and pg_receivewal used 0/1000000 as the starting WAL position.
True, thank you very much!
>
> Regards,
>
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2020-09-25 09:52:18 | Memory leak in RelationBuildRowSecurity |
| Previous Message | Michał Albrycht | 2020-09-25 07:55:57 | Re: BUG #16634: Conflicting names of indexes for partitioned tables |