From: | Ankush Chawla <ankushchawla03(at)gmail(dot)com> |
---|---|
To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: hot standby in Postgresql 12 |
Date: | 2021-01-19 06:17:09 |
Message-ID: | CAOY8JhA6Ki2i_CvQLgu94t=NxcMb4k6N_MiS3nM1j=_qaGH2MA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Still the same :
checkpoint;
select pg_switch_wal();
loading few tables and did a switch as well , still the same, not able to
connect to standby database
*psql: error: FATAL: the database system is starting up*
On Tue, Jan 19, 2021 at 11:18 AM Paul Förster <paul(dot)foerster(at)gmail(dot)com>
wrote:
> Hi David,
>
> > On 19. Jan, 2021, at 04:48, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> >
> > And now the standby is waiting for the next wal file to be archived by
> the primary. You should probably set archive_timeout to a non-zero value
> since the primary doesn’t seem very busy (though you also still need to do
> at least one write, empty wal files don’t get rotated out and archived.)
>
> you should be able to get around your problem by doing the following on
> the primary database:
>
> checkpoint;
> select pg_switch_wal();
>
> The pg_switch_wal() alone will not trigger WAL file generation if no
> transaction has been going on. That's why I recommend forcing a checkpoint
> before that (same with Oracle by the way).
>
> As soon as a WAL is generated, it should get shipped to the standby
> database. Then it should open.
>
> Cheers,
> Paul
--
Best Regards,
Ankush Chawla
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-01-19 06:26:39 | Re: hot standby in Postgresql 12 |
Previous Message | Paul Förster | 2021-01-19 05:48:17 | Re: hot standby in Postgresql 12 |