From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | andrey(dot)arapov(at)nixaid(dot)com |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] initdb: do not exit after warn_on_mount_point |
Date: | 2022-09-11 10:17:47 |
Message-ID: | 20220911101747.r255dgsd673tb7qa@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Sat, Sep 10, 2022 at 07:14:59PM +0000, andrey(dot)arapov(at)nixaid(dot)com wrote:
>
> Have slightly improved the logic so that it does not report an error
> "directory \"%s\" exists but is not empty"
> when it is only supposed to warn the user about the mountpoint, without
> exiting.
>
> To me, my patch looks like a typo fix where exit(1) should not be called on
> the warn_on_mount_point(), but only warn and continue as more people are
> mounting the device at `/var/lib/postgresql/data` (PGDATA) in the
> containerized world (K8s deployments, especially now in the Akash Network I
> am working for) for making sure their data persist.
This definitely isn't a typo, as it's really strongly discouraged to use a
mount point for the data directory. You can refer to this thread [1] for more
explanations.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2022-09-11 10:42:03 | Check SubPlan clause for nonnullable rels/Vars |
Previous Message | Aleksander Alekseev | 2022-09-11 10:06:07 | Re: [PATCH] Clarify the comments about varlena header encoding |