From c3d8523951c6736e55da870ab622cc0c34d57011 Mon Sep 17 00:00:00 2001
From: "Jonathan S. Katz"
The PostgreSQL Committers
are the people with access to push to the
- git repository.
+ git repository.
Security Team
diff --git a/templates/pages/about/governance/sysadmin.html b/templates/pages/about/governance/sysadmin.html
index 0e48f20..5fde2c2 100644
--- a/templates/pages/about/governance/sysadmin.html
+++ b/templates/pages/about/governance/sysadmin.html
@@ -11,7 +11,7 @@
is discussed on the
pgsql-www mailing list.
Source code for the postgresql.org web site is stored in a public
- GIT repository.
+ GIT repository.
Last updated: September 21, 2023. {%git_changes_link%} View history before December 8, 2020.
+Last updated: September 21, 2023. {%git_changes_link%} View history before December 8, 2020.
The Community Conference Recognition programme is a voluntary scheme under which submitters of events to the PostgreSQL Website listings may self-assess their entry against the criteria below, and if they comply may market their event as a PostgreSQL Community event.
diff --git a/templates/pages/about/policies/npos.html b/templates/pages/about/policies/npos.html index cc8ac37..303dba1 100644 --- a/templates/pages/about/policies/npos.html +++ b/templates/pages/about/policies/npos.html @@ -5,7 +5,7 @@Last updated: January 7, 2025. {%git_changes_link%} View history before December 8, 2020.
+Last updated: January 7, 2025. {%git_changes_link%} View history before December 8, 2020.
Recognised PostgreSQL Nonprofit Organisations (NPOs) will be listed on the PostgreSQL Website as such. To become recognised as an NPO, the organisation must self-certify that they meet the criteria below, aimed at ensuring they meet the standards of openness expected in the PostgreSQL Community.
diff --git a/templates/pages/developer/backend.html b/templates/pages/developer/backend.html index a556644..38ff210 100644 --- a/templates/pages/developer/backend.html +++ b/templates/pages/developer/backend.html @@ -46,14 +46,14 @@ echo "0, 0," | awk -F, '{printf "%d, %d\n", $1 + 145, $2 + 45}' or Unix Domain sockets. It is loaded into a string, and passed to the parser, where the lexical scanner, scan.l, +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/backend/parser/scan.l">scan.l, breaks the query up into tokens(words). The parser uses gram.y +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/backend/parser/gram.y">gram.y and the tokens to identify the query type, and load the proper query-specific structure, like CreateStmt +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/parsenodes.h">CreateStmt or SelectStmt. +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/parsenodes.h">SelectStmt.The statement is then identified as complex (SELECT / INSERT / UPDATE / DELETE) or simple, e.g CREATE ROLE, ANALYZE, @@ -62,27 +62,27 @@ functions in the Query +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/parsenodes.h">Query structure that contains all the elements used by complex queries. Query.jointree holds the FROM and WHERE clauses, which is filled in by transformFromClause() and -transformWhereClause(). +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/backend/parser/parse_clause.c">transformFromClause() and +transformWhereClause(). Each table referenced in the query is represented by a RangeTblEntry, +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/parsenodes.h">RangeTblEntry, and they are linked together to form the range table of the query, which is generated by transformFromClause(). +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/backend/parser/parse_clause.c">transformFromClause(). Query.rtable holds the query's range table.
Certain queries, like SELECT, return columns of data. Other queries, like INSERT and UPDATE, specify the columns modified by the query. These column references are converted to TargetEntry +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/primnodes.h">TargetEntry entries, which are linked together to make up the target list of the query. The target list is stored in Query.targetList, which is generated by transformTargetList().
+href="https://git.postgresql.org/cgit/postgresql.git/tree/src/backend/parser/parse_target.c">transformTargetList().Other query elements, like aggregates(SUM()), GROUP BY, and ORDER BY are also stored in their own Query @@ -100,7 +100,7 @@ type of each table in the RangeTable, using Query.jointree(FROM and WHERE clauses) to consider optimal index usage.
The path module then generates an optimal Plan, +href="https://git.postgresql.org/cgit/postgresql.git/tree/src/include/nodes/plannodes.h">Plan, which contains the operations to be performed to execute the query.The Plan is then passed to the Code access and information
-
Search Code By Git Commit Hash