From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Additional role attributes && superuser review |
Date: | 2014-10-16 10:44:43 |
Message-ID: | CA+U5nM+JxVvQ_07774Ty6KMChsNPTmS1v7JtqeA=TD8uTnv7Ww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 15 October 2014 06:22, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> BACKUP:
> pg_start_backup()
> pg_stop_backup()
> pg_switch_xlog()
> pg_create_restore_point()
Yes, but its more complex. As Jim says, you need to include pg_dump,
plus you need to include the streaming utilities, e.g. pg_basebackup.
> LOGROTATE:
> pg_rotate_logfile()
Do we need one just for that?
> MONITOR:
> View detailed information regarding other processes.
> pg_stat_get_wal_senders()
> pg_stat_get_activity()
+1
> Connect using 'reserved' slots
> This is another one which we might add as another role attribute.
RESERVED?
Perhaps we need a few others also - BASHFUL, HAPPY, GRUMPY etc
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2014-10-16 11:04:28 | Re: Performance regression: 9.2+ vs. ScalarArrayOpExpr vs. ORDER BY |
Previous Message | Simon Riggs | 2014-10-16 10:26:27 | Re: Deferring some AtStart* allocations? |