Functions ...................................................................... 969 34.3. Command Execution Functions .................................................................. 976 34.4. Asynchronous authentication failure ............................................... 2802 F.4. auto_explain — log execution plans of slow queries ...................................... 2803 F.5. basebackup_to_shell — example ......................... 2932 F.32. pg_stat_statements — track statistics of SQL planning and execution ............... 2934 F.33. pgstattuple — obtain tuple-level statistics ........................

Functions ...................................................................... 997 32.3. Command Execution Functions ................................................................ 1004 32.4. Asynchronous authentication failure ............................................... 2857 F.3. auto_explain — log execution plans of slow queries ...................................... 2858 F.4. basebackup_to_shell — example ......................... 2985 F.30. pg_stat_statements — track statistics of SQL planning and execution ............... 2987 F.31. pgstattuple — obtain tuple-level statistics ........................

Status Functions ................................................................ 921 34.3. Command Execution Functions ............................................................. 928 34.4. Asynchronous Command authentication failure .......................................... 2659 F.4. auto_explain — log execution plans of slow queries ................................. 2660 F.5. basebackup_to_shell — example ......................... 2785 F.32. pg_stat_statements — track statistics of SQL planning and execution ......... 2787 F.33. pgstattuple — obtain tuple-level statistics ..............................

Status Functions ................................................................ 947 32.3. Command Execution Functions ............................................................. 954 32.4. Asynchronous Command authentication failure .......................................... 2701 F.3. auto_explain — log execution plans of slow queries ................................. 2702 F.4. basebackup_to_shell — example ......................... 2825 F.30. pg_stat_statements — track statistics of SQL planning and execution ......... 2827 F.31. pgstattuple — obtain tuple-level statistics ..............................

Functions ...................................................................... 907 34.3. Command Execution Functions .................................................................. 913 34.4. Asynchronous initial concepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process

Functions ...................................................................... 879 33.3. Command Execution Functions .................................................................. 886 33.4. Asynchronous initial concepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process

Status Functions ................................................................ 863 34.3. Command Execution Functions ............................................................. 869 34.4. Asynchronous Command initial con- cepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process

Status Functions ................................................................ 835 33.3. Command Execution Functions ............................................................. 841 33.4. Asynchronous Command initial con- cepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process

Functions ...................................................................... 790 33.3. Command Execution Functions .................................................................. 796 33.4. Asynchronous initial concepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process

Functions ...................................................................... 873 33.3. Command Execution Functions .................................................................. 879 33.4. Asynchronous initial concepts for the system were presented in [ston86], and the definition of the initial data model appeared in [rowe87]. The design of the rule system at that time was described in [ston87a]. The rationale interact will make this chapter somewhat clearer. In database jargon, PostgreSQL uses a client/server model. A PostgreSQL session consists of the following cooperating processes (programs): • A server process