agora inbox for pgsql-hackers@postgresql.orghelp / color / mirror / Atom feed
[PATCH 2/3] Fix "accesses" per suggestion from Erik 2+ messages / 2 participants [nested] [flat]
* [PATCH 2/3] Fix "accesses" per suggestion from Erik @ 2020-10-31 20:48 Justin Pryzby <pryzbyj@telsasoft.com> 0 siblings, 0 replies; 2+ messages in thread From: Justin Pryzby @ 2020-10-31 20:48 UTC (permalink / raw) --- doc/src/sgml/architecture.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/architecture.sgml b/doc/src/sgml/architecture.sgml index ffdac61975..6f819220dc 100644 --- a/doc/src/sgml/architecture.sgml +++ b/doc/src/sgml/architecture.sgml @@ -158,7 +158,7 @@ --> <para> - The Statistics Collector collects counters about accesses to + The Statistics Collector collects counters about access to SQL objects like tables, rows, indexes, pages, and more. It stores the obtained information in system tables. </para> @@ -423,7 +423,7 @@ <para> A first approach to implement protections against concurrent - accesses to the same data may be the locking of critical + access to the same data may be the locking of critical rows. Two such techniques are: <emphasis>Optimistic Concurrency Control</emphasis> (OCC) and <emphasis>Two Phase Locking</emphasis> (2PL). @@ -479,7 +479,7 @@ </para> <para> - So, what's going on in detail when write accesses take place? + So, what's going on in detail when write access takes place? <xref linkend="tutorial-mvcc-figure"/> shows details concerning <literal>xmin</literal>, <literal>xmax</literal>, and user data. </para> @@ -1059,7 +1059,7 @@ The setting of the flags is silently done by <command>VACUUM</command> and Autovacuum during their bloat and freeze operations. This is done to speed up future vacuum actions, - regular accesses to heap pages, and some accesses to + regular access to heap pages, and some access to the index. Every data-modifying operation on any row version of the page clears the flags. </para> -- 2.17.0 --aVD9QWMuhilNxW9f Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0003-More-fixes-on-top.patch" ^ permalink raw reply [nested|flat] 2+ messages in thread
* [PATCH v1] Allow pg_read_all_stats to see database size in \l+ @ 2026-07-22 11:16 Christoph Berg <myon@debian.org> 0 siblings, 0 replies; 2+ messages in thread From: Christoph Berg @ 2026-07-22 11:16 UTC (permalink / raw) The server already allowed members of pg_read_all_stats to see the size of all databases, but psql's \l+ was too restrictive. --- src/bin/psql/describe.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/bin/psql/describe.c b/src/bin/psql/describe.c index a2f09c26369..ad9c8affb4f 100644 --- a/src/bin/psql/describe.c +++ b/src/bin/psql/describe.c @@ -986,7 +986,8 @@ listAllDbs(const char *pattern, bool verbose) printACLColumn(&buf, "d.datacl"); if (verbose) appendPQExpBuffer(&buf, - ",\n CASE WHEN pg_catalog.has_database_privilege(d.datname, 'CONNECT')\n" + ",\n CASE WHEN pg_catalog.has_database_privilege(d.datname, 'CONNECT') OR\n" + " pg_catalog.pg_has_role('pg_read_all_stats', 'USAGE')\n" " THEN pg_catalog.pg_size_pretty(pg_catalog.pg_database_size(d.datname))\n" " ELSE 'No Access'\n" " END as \"%s\"" -- 2.53.0 --bukXArRbhiisqidC-- ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-07-22 11:16 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2020-10-31 20:48 [PATCH 2/3] Fix "accesses" per suggestion from Erik Justin Pryzby <pryzbyj@telsasoft.com> 2026-07-22 11:16 [PATCH v1] Allow pg_read_all_stats to see database size in \l+ Christoph Berg <myon@debian.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox