public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Benjamin Wang <[email protected]>
Cc: Peter J. Holzer <[email protected]>
Cc: [email protected]
Subject: Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
Date: Mon, 14 Jul 2025 15:10:45 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADVOZZ5D7bR_2fcqonVc5CE6wkwDb1smzZf+V7MVspw+1NKhRQ@mail.gmail.com>
References: <CAGOe9RiRUK9K8gUbsMfg8nWDsM2Fd9py-2oe4VG1Uaggu8fQGA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CADVOZZ5D7bR_2fcqonVc5CE6wkwDb1smzZf+V7MVspw+1NKhRQ@mail.gmail.com>

Benjamin Wang <[email protected]> writes:
> I am not sure whether PostgreSQL depends on system call `fsyncdata` to
>  sync data to disk. If yes, then I don't think it's safe to use NFS.

Well, that's a whole other discussion.  The point about mount
directories applies to any sort of dismountable storage.

(But I too would not use Postgres-over-NFS for any critical data.
Too many moving parts.  It's tough enough to ensure crash safety
with local storage.)

			regards, tom lane

view thread (3+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox