| From: | Jason Long <hack3rcon(at)yahoo(dot)com> |
|---|---|
| To: | folarte(at)peoplecall(dot)com |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Read-only mode usage |
| Date: | 2024-02-28 15:43:32 |
| Message-ID: | 846580225.1063051.1709135012618@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,1- What does it mean, not the whole database?
2- Can this be considered a kind of guard?
3- Can you tell me a read-only scenario? For example, if we have three servers, then one of the servers can be the main server and the other two servers can be read only.
On Wed, Feb 28, 2024 at 4:24 PM, Francisco Olarte<folarte(at)peoplecall(dot)com> wrote: On Wed, 28 Feb 2024 at 13:34, Jason Long <hack3rcon(at)yahoo(dot)com> wrote:
> What is the use of a database in read-only mode?
Normally it is a connection/session to the database what is in
read-only mode, not the whole database.
As it has been pointed out, you connect in read only mode to read, so
you are protected from accidental modifications. Also, knowing your
transactions are not going to write make life easier for optimizers
and other things.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shanti-Dominique | 2024-02-28 15:49:40 | Re: Efficient rows filter for array inclusion with gin index |
| Previous Message | Jason Long | 2024-02-28 15:36:29 | Re: PostgreSQL Guard |