Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table - Mailing list pgsql-docs

From Daniel Gustafsson
Subject Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Date
Msg-id 99AC5F34-FDB6-42A8-867A-CF97F0707F9B@yesql.se
Whole thread Raw
In response to Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table  (Maxim Yablokov <m.yablokov@postgrespro.ru>)
Responses Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
List pgsql-docs
> On 26 Oct 2023, at 09:33, Maxim Yablokov <m.yablokov@postgrespro.ru> wrote:

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

Interesting catch, time_dimension has been unused since introduced with commit
a294726bc1d (in 2005), and the archives doesn't provide any further insights.
While I don't have access to the book referred to for the example, we don't
expect our readers to either so it seems to me that we could remove it from the
example to avoid risk of confusion. Would you like to propose a patch for this?

--
Daniel Gustafsson




pgsql-docs by date:

Previous
From: Maxim Yablokov
Date:
Subject: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Next
From: Maxim Yablokov
Date:
Subject: Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table