From 7f61f8a71f81762de04e2ff609b1e66b17405aa2 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 21 Jul 1998 04:19:44 +0000 Subject: [PATCH] Update. --- src/tools/backend/index.html | 66 +++++++++++++++++------------------- 1 file changed, 32 insertions(+), 34 deletions(-) diff --git a/src/tools/backend/index.html b/src/tools/backend/index.html index 626517293cd..51e4972037f 100644 --- a/src/tools/backend/index.html +++ b/src/tools/backend/index.html @@ -10,7 +10,39 @@ How PostgreSQL Processes a Query by Bruce Momjian

+

+ +Click on an item to see more detail or look at the full +index. + +
+
+flowchart +
+ + + + + + + + + + + + + + + + + + + +
+

+

+

A query comes to the backend via data packets arriving through TCP/IP or Unix Domain sockets. It is loaded into a string, and passed to the @@ -87,40 +119,6 @@ They can be accessed by clicking on the flowchart.

-

- -Click on an item to see more detail or look at the full -index. - -
-
-flowchart -
- - - - - - - - - - - - - - - - - - - -
-

- -

-

- Another area of interest is the shared memory area, which contains data accessable to all backends. It has table recently used data/index blocks, locks, backend information, and lookup tables for these