| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Maxim Yablokov <m(dot)yablokov(at)postgrespro(dot)ru> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table |
| Date: | 2023-10-26 09:29:40 |
| Message-ID: | 99AC5F34-FDB6-42A8-867A-CF97F0707F9B@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
> On 26 Oct 2023, at 09:33, Maxim Yablokov <m(dot)yablokov(at)postgrespro(dot)ru> wrote:
> 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)?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Yablokov | 2023-10-26 09:36:02 | Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table |
| Previous Message | Maxim Yablokov | 2023-10-26 07:33:50 | Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table |