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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: dilipbalaut(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, michael(at)paquier(dot)xyz, rjuju123(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Date: 2022-07-13 16:43:45
Message-ID: 20220713164345.j3n67rc45rpa4vop@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Not a review, just a preparatory rebase across some trivially
conflicting changes. I also noticed that
src/test/recovery/t/, which was added two days
after v23 was sent, and which uses allow_in_place_tablespaces, bails out
because of the checks introduced by this patch, so I made the check
routine do nothing in that case.

Anyway, here's v24.

Álvaro Herrera Breisgau, Deutschland —
"La conclusión que podemos sacar de esos estudios es que
no podemos sacar ninguna conclusión de ellos" (Tanenbaum)

Attachment Content-Type Size
v24-0001-Fix-replay-of-create-database-records-on-standby.patch text/x-diff 18.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-13 17:00:36 Re: make update-po@master stops at pg_upgrade
Previous Message Isaac Morland 2022-07-13 16:33:12 Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.