From: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regression test PANICs with master-standby setup on same machine |
Date: | 2019-04-22 12:51:00 |
Message-ID: | CAGz5QCJc7aULrQaZ4PGnx_xD-uFhZZ15GD3PxFqp25KW3e3=ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 22, 2019 at 6:07 PM Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> If you don't have a problem using TAP test suite, tablespace is
> allowed with a bit restricted steps using the first patch in my
> just posted patchset[1]. This will work for you if you are okay
> with creating a standby after creating a tablespace. See the
> second patch in the patchset.
>
> If you stick on shell script, the following steps allow tablespaces.
>
> 1. Create tablespace directories for both master and standby.
> 2. Create a master then start.
> 3. Create tablespaces on the master.
> 4. Create a standby using pg_basebackup --tablespace_mapping=<mstdir>=<sbydir>
> 5. Start the standby.
>
> [1] https://www.postgresql.org/message-id/20190422.211933.156769089.horiguchi.kyotaro@lab.ntt.co.jp
>
Thank you for the info. I'll try the same.
--
Thanks & Regards,
Kuntal Ghosh
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2019-04-22 13:12:16 | Re: Runtime pruning problem |
Previous Message | Etsuro Fujita | 2019-04-22 12:45:36 | Re: pgsql: Allow insert and update tuple routing and COPY for foreign table |