Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table

Поиск
Список
Период
Сортировка
От Maxim Yablokov
Тема Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Дата
Msg-id fe405123-9cae-4f16-81c0-4e73bec93b81@postgrespro.ru
обсуждение исходный текст
Ответ на Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table  (Daniel Gustafsson <daniel@yesql.se>)
Ответы Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table  (Daniel Gustafsson <daniel@yesql.se>)
Список pgsql-docs

I believe that the attached patch should fix this problem. Please have a look.

26.10.2023 12:29, Daniel Gustafsson пишет:
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 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

--
Best regards,
Maxim Yablokov
Technical writer-translator
Postgres Professional
Вложения

В списке pgsql-docs по дате отправления:

Предыдущее
От: Maxim Yablokov
Дата:
Сообщение: Re: Example 43.6. A PL/pgSQL Trigger Function for Maintaining a Summary Table
Следующее
От: PG Doc comments form
Дата:
Сообщение: pg_isready --dbname option is broken. So it should not be in the manual