public inbox for [email protected]  

help / color / mirror / Atom feed
From: SATYANARAYANA NARLAPURAM <[email protected]>
To: Andrei Lepikhov <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Jack Bonatakis <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: Read-only connection mode for AI workflows.
Date: Thu, 19 Mar 2026 12:39:18 -0700
Message-ID: <CAHg+QDfVrkwmYnGPi9uPJMtcvMhFLhyeDPRx-nLNckKg5UtanQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CADsUR0B9bcJQKYHyUMnWcODGzF5+AdeToawULkkTKfrq32Z-8w@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<wf3p4636lgu67rwatc7pdnvmz36guljm3lzatvvy45ew3adtvw@ip7yivjxqqy6>
	<[email protected]>

Hi,

On Wed, Mar 18, 2026 at 7:36 AM Andrei Lepikhov <[email protected]> wrote:

> On 18/3/26 15:26, Andres Freund wrote:
> > Regardless of the AI angle it's quite useful to be able to put a server
> into
> > read only mode, e.g. in preparation for a planned failover where you can
> > continue to allow reads but don't want any more writes. Or in
> preparation for
> > a shutdown you want to prevent further writes (so the shutdown
> checkpoint is
> > quick), but you do want to allow further reads (to reduce the scope of
> the
> > downtime, by allowing reads while doing a CHECKPOINT before the actual
> > shutdown).
>
> It returns us to the question about cluster-wide V/S session-wide
> read-only mode. Should we design one of them or consider both? What do
> you think?
>

+1 to scenarios Andres' mentioned. Additional cases where a cluster‑wide
setting is helpful include disk‑full events and policy enforcement, where
write access is revoked but read access is preserved for data exfiltration.
Session level is helpful for the AI use cases or to provide controlled user
access. I see value in supporting both.

 Thanks,
Satya


view thread (20+ messages)  latest in thread

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], [email protected], [email protected]
  Subject: Re: Read-only connection mode for AI workflows.
  In-Reply-To: <CAHg+QDfVrkwmYnGPi9uPJMtcvMhFLhyeDPRx-nLNckKg5UtanQ@mail.gmail.com>

* 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