Re: A proposal for shared memory based backup infrastructure

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: mahendrakar s <mahendrakarforpg(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, arorasam(at)gmail(dot)com, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
Subject: Re: A proposal for shared memory based backup infrastructure
Date: 2022-08-05 15:55:33
Message-ID: CA+TgmoaU6ftky3HBn8bB747HzDXJAWMvHXpecgycgpn94a-UeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 30, 2022 at 2:54 AM mahendrakar s
<mahendrakarforpg(at)gmail(dot)com> wrote:
> There might be security concerns if the backup started by one user can be stopped by another user.
> This is because the user who stops the backup will get the backup_label or table space map file contents of other user.
> Isn't this a concern for non-exclusive backup?

This doesn't seem like a real problem. If you can take a backup,
you're already a highly-privileged user.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-08-05 16:04:43 pgsql: BRIN: mask BRIN_EVACUATE_PAGE for WAL consistency checking
Previous Message Justin Pryzby 2022-08-05 15:16:45 Re: Expr. extended stats are skipped with equality operator