Re: standby recovery fails (tablespace related) (tentative patch and discussion)

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: rjuju123(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Date: 2022-01-20 04:25:41
Message-ID: 20220120.132541.1317539805818231991.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Mon, 17 Jan 2022 17:24:43 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Sun, 16 Jan 2022 12:43:03 +0800, Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote in
> > I'm not very familiar with windows, but maybe using strawberry perl instead
> > ([1]) would fix your problem? I think it's also quite popular and is commonly
> > used to run pgBadger on Windows.
>
> Thanks! I'll try it later.

Build is stopped by some unresolvable symbols.

Strawberry perl is 5.28, which doesn't expose new_ctype, new_collate
and new_numeric according the past discussion. (Active perl is 5.32).

https://www.postgresql.org/message-id/20200501134711.08750c5f%40antares.wagner.home

However, the patch provided revealed other around 70 unresolved symbol
errors...

# Hmm. perl on CentOS 8 is 5.26..

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-01-20 04:38:45 Re: pg_upgrade should truncate/remove its logs before running
Previous Message Peter Smith 2022-01-20 04:21:13 Re: row filtering for logical replication