Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.

Поиск
Список
Период
Сортировка
От Joel Jacobson
Тема Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Дата
Msg-id CAASwCXd3Tng9a694gmpGj+Ed2ZZRTDg5RrV+OLGiXy7RsguOaQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.  (Joel Jacobson <joel@trustly.com>)
Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
On Sat, Mar 12, 2016 at 4:41 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> I afraid so you try to look on your use case as global/generic issue. The
> PL/SQL, ADA. PL/pgSQL are verbose languages, and too shortcuts does the
> languages dirty. In this point we have different opinion.
>
> I proposed some enhanced PLpgSQL API with a possibility to create a
> extension that can enforce your requested behave. The implementation can not
> be hard, and it can coverage some special/individual requests well.

I'm not at all interested to discuss any of the proposed changes that
have already been proposed,
because we have already had lengthy discussions on them, and I doubt
neither you nor me have nothing to add.

What we need is more input on proposed changes from other companies
who are also heavy users of PL/pgSQL.

Only then can we move forward. It's like Robert is saying, there is a
risk for bikeshedding here,
we must widen our perspectives and get better understanding for how
other heavy users are using PL/pgSQL.

Pavel, do you know of any such companies?



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: amcheck (B-Tree integrity checking tool)
Следующее
От: Joel Jacobson
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.