On Wed, Dec 22, 2021 at 7:20 AM Dilip Kumar wrote:
> On Wed, 22 Dec 2021 at 12:28 AM, Ashutosh Sharma
> wrote:
>
>>
>> Is it okay to share the same tablespace (infact relfile) between the
>> primary and standby server? Perhaps NO.
>>
>
>> Oops, yeah absolutely they can never share the tablespace
On Wed, 22 Dec 2021 at 12:28 AM, Ashutosh Sharma
wrote:
>
> Is it okay to share the same tablespace (infact relfile) between the
> primary and standby server? Perhaps NO.
>
> Oops, yeah absolutely they can never share the tablespace path. So we can
ignore this issue.
—
Dilip
--
Regards,
Dilip
This is happening because in the case of the primary server, we let the
checkpointer process to unlink the first segment of the rel file but
that's not the case with the standby server. In case of standby, the
startup/recovery process unlinks the first segment of the rel file
immediately during WAL
While testing the below case with the hot standby setup (with the
latest code), I have noticed that the checkpointer process crashed
with the $subject error. As per my observation, we have registered the
SYNC_REQUEST when inserting some tuple into the table, and later on
ALTER SET TABLESPACE we hav
