On Mon, 2020-03-30 at 11:02 +0530, Shishir Joshi wrote:
> On Fri, 27 Mar 2020 at 19:30, Tom Lane wrote:
> > Shishir Joshi writes:
> > > I recently faced an issue with PG 11 where the VM that the PG process was
> > > running on got restarted because of a hardware issue. After the VM
> > > restart
Hi Tom,
I forgot to mention, but in this case it looks the mount was completed
before the PG process was started up. But we don't have an explicit check
for making sure the file system is present in the start script. Thanks for
the tip.
On Fri, 27 Mar 2020 at 19:30, Tom Lane wrote:
> Shishir Jos
Shishir Joshi writes:
> I recently faced an issue with PG 11 where the VM that the PG process was
> running on got restarted because of a hardware issue. After the VM restart,
> the Postgres process failed to start on the 1st attempt with the error "*LOG:
> could not open directory "pg_tblspc/163
Hello,
I recently faced an issue with PG 11 where the VM that the PG process was
running on got restarted because of a hardware issue. After the VM restart,
the Postgres process failed to start on the 1st attempt with the error "*LOG:
could not open directory "pg_tblspc/16388/PG_11_201809051": No
