On Thu, Jul 18, 2019 at 10:09 PM Matthew Pounsett wrote:
> That would likely keep the extra storage requirements small, but still
> non-zero. Presumably the upgrade would be unnecessary if it could be done
> without rewriting files. Is there any rule of thumb for making sure one has
> enough
On 7/30/19 12:58 AM, Luca Ferrari wrote:
On Tue, Jul 30, 2019 at 2:50 AM Marcos Aurelio Nobre
wrote:
I was wondering if it was possible to configure the pgAdmin4 menus to be available
for a particular login, only Backup & Restore items. But I'm not sure how to
associate a bank login account w
On Tue, Jul 30, 2019 at 2:22 PM Ron wrote:
> Luca, it is common some large Enterprise environments to have Operations
> staff that can run backups without being able to do anything else. For
> example, SQL Server has a per-database user mapping named db_backupoperator.
Yes, but I think here we
I've also been thinking about this possibility. Create a Linux (S.O.) user
account that has the ability to run pg_dump and pg_restore and enable this
user account to be able to connect to a database - I believe this is
possible through PG_HBA.CONF
But I don't know how to implement this on Linux, n
On Wed, Jul 31, 2019 at 2:48 AM Marcos Aurelio Nobre
wrote:
> But I don't know how to implement this on Linux, nor how to write this entry
> in the pg_hba.conf file.
I would start with an entry in pg_hba.conf like the following:
hostall pg_backup_usernamelocalhost
