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

From: Joel Jacobson <joel(at)trustly(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)trustly(dot)com>
Subject: Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Date: 2016-03-11 22:22:13
Message-ID: CAASwCXfEUGC0ePtuJJ8p1ZVrtCm90tfDTmjeGjX2nquNjMMoCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Mar 12, 2016 at 5:09 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> 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.
>
>
> I disagree with this opinion - this is community sw, not commercial. We can
> do nothing if we don't find a agreement.

I disagree with your disagreement.

The users are what matters, and many of them are of course not on this
list (since this is a list for hackers), so we need to reach out to
the users, and those are companies/websites/nonprofits/governments.
So discussing proposed changes on this list will take us absolutely
nowhere, without further input from actual heavy users.
Once we do have input from the heavy users, then and only then can we
continue discussing things on this list, but before then it's kind of
pointless, because we don't know what the most commonly proposed
changes are, not you, not me. The risk of bikeshedding is just too
big, like Robert pointed out.

>> Pavel, do you know of any such companies?
> Probably the biggest company with pretty large code of PL/pgSQL was Skype,
> but I have not any info about current state.

True! I had almost forgotten about them after Microsoft acquired them.
Let's hope they are still on PostgreSQL. I'll check it out, thanks.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Pavel Stehule 2016-03-11 22:30:26 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Previous Message Pavel Stehule 2016-03-11 22:09:57 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-03-11 22:30:26 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Previous Message Andres Freund 2016-03-11 22:15:21 Re: Background Processes and reporting