Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvusW-008VQS-4q for pgsql-docs@arkaria.postgresql.org; Thu, 26 Oct 2023 07:34:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qvusU-00E3cD-MF for pgsql-docs@arkaria.postgresql.org; Thu, 26 Oct 2023 07:34:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvusU-00E3c4-AA for pgsql-docs@lists.postgresql.org; Thu, 26 Oct 2023 07:34:02 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qvusQ-002Ms4-St for pgsql-docs@lists.postgresql.org; Thu, 26 Oct 2023 07:34:01 +0000 Received: from [172.30.2.10] (unknown [172.30.2.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: m.yablokov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 437A5E20E62 for ; Thu, 26 Oct 2023 10:33:56 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1698305636; bh=RojBj7+3f9WN0WaOmD8+RO1CBNnor+1W4alvuOKT6HU=; h=Message-ID:Date:User-Agent:To:From:Subject:From; b=pEKc2RaNLRF2e6t/EfDH9z0+87g7m5CMI66YnqP2hEMa2eqFvDzpCQmEXkgKE5OkT qFSbaR7FFlFb7Hm/cOQw5Syzp5h2P5Fh8kc8Kt270qDWPYKpWA/30srxlVMQ0W4+f0 uax+3GvJrTjxGRDDXBgl4qEFAEelSlB2Uaf4OdFBDzI8zwrOrEVGPC4INSByH+NMgg JbGsPYhm+4tGFtfy+21EF/PnQcrXI4L1ug0tSaboBcYUDYYQqM/n1U60zf2ptS5T7F VzzwRGTAbh2yZxlRVVHEvJJCNzSWgItl2VDNRLNj7NZiuqGm7PzkfqjYL0LDJANy8K 1LbBsCNFec/+Q== Content-Type: multipart/alternative; boundary="------------hoAPHeyt7IzRCRVjzJNNLMjZ" Message-ID: <70f74895-8512-4b2f-8617-2ac0ebcd2e87@postgrespro.ru> Date: Thu, 26 Oct 2023 10:33:50 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: pgsql-docs@lists.postgresql.org From: Maxim Yablokov Subject: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table Organization: Postgres Professional List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------hoAPHeyt7IzRCRVjzJNNLMjZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello! Example 43.6 on the page https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called main. But it seems that the table *time_dimension* is not used any further, it's a bit strange for one of main tables of the example. Am I missing something, or should this example be extended (or reduced)? -- Best regards, Maxim Yablokov Technical writer-translator Postgres Professional --------------hoAPHeyt7IzRCRVjzJNNLMjZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hello!

Example 43.6 on the page https://www.postgresql.org/docs/16/plpgsql-trigger.html has two tables called main. But it seems that the table time_dimension is not used any further, it's a bit strange for one of main tables of the example. Am I missing something, or should this example be extended (or reduced)?

--
Best regards,
Maxim Yablokov
Technical writer-translator
Postgres Professional
--------------hoAPHeyt7IzRCRVjzJNNLMjZ--