[DOCS] simple wording fix
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/static/parallel-plans.html Description: Hi! In the first paragraph of the second part of the third sentence, this: "it must constructed so that each process which executes the plan" should be: "it must be constructed so that each process which executes the plan". That is, the "be" is missing. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] monitoring.sgml - clarify length of query text displayed in pg_stat_statements
Hi Small doc patch to clarify how much of the query text is show in pg_stat_statements and a link to the relevant GUC. Regards Ian Barwick -- Ian Barwick http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml new file mode 100644 index 3de489e..02dab87 *** a/doc/src/sgml/monitoring.sgml --- b/doc/src/sgml/monitoring.sgml *** postgres 27093 0.0 0.0 30096 2752 *** 785,791 Text of this backend's most recent query. If state is active this field shows the currently executing query. In all other states, it shows the last query ! that was executed. --- 785,793 Text of this backend's most recent query. If state is active this field shows the currently executing query. In all other states, it shows the last query ! that was executed. By default the query text is truncated at 1024 ! characters; this value can be changed via the parameter ! . -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] Performance Issue after implementataion Row level Secuirty
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.5/static/ddl-rowsecurity.html Description: We have implemented Row Level Security feature in postgres database but database is working very slow after implementation of RLS(Row level Security) and getting frequent AccessShareLock. we 1.created role. 2.grant permission to table, sequence. 3.enabled row level security and then created policy. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
