On Oct 7, 2021, at 19:38, Bruce Momjian wrote:
>
> On Thu, Oct 7, 2021 at 07:15:39PM -0700, Jeremy Schneider wrote:
>> PostgreSQL added wait events starting in 9.6 and the last thing that's
>> missing is an integrated way to trace or log them. A simple starting
>> point could be a session-lev
On 10/7/21 22:15, Jeremy Schneider wrote:
On 10/5/21 13:24, Peter Geoghegan wrote:
On Fri, Oct 1, 2021 at 1:06 PM Jeff Holt wrote:
Now looking closely at postgreSQL, I see an opportunity to more quickly
implement Oracle's current feature list.
I've come to this point because I see many roa
On Thu, Oct 7, 2021 at 07:15:39PM -0700, Jeremy Schneider wrote:
> PostgreSQL added wait events starting in 9.6 and the last thing that's
> missing is an integrated way to trace or log them. A simple starting
> point could be a session-level GUC that enables a hook in
> pgstat_report_wait_start()
On 10/5/21 13:24, Peter Geoghegan wrote:
> On Fri, Oct 1, 2021 at 1:06 PM Jeff Holt wrote:
>> Now looking closely at postgreSQL, I see an opportunity to more quickly
>> implement Oracle's current feature list.
>>
>> I've come to this point because I see many roadblocks for users who want to
>> s
On Mon, Oct 4, 2021 at 08:34:29AM +0200, Laurenz Albe wrote:
> > Now looking closely at postgreSQL, I see an opportunity to more quickly
> > implement Oracle's current feature list.
>
> Anything that improves user experience in that respect is welcome, but
> consider
> that each database has di
>
>
>
> This won't be immediately useful, but there's been a patch proposed for
> Postgres 15 to allow logging the plan of a running query [1]. Progress
> seems to have stalled a bit, but it seems like there was a fair amount of
> interest, so I wouldn't count it out yet. If you have thoughts on th
