Hi!

Attached patch implements a column in the server status view that shows if
a transaction is blocked, and what process it's blocked by.

Since we're very close to RC, I'm sending it past here before doing
anything more. What do ppl think, are we ok with something like this for
this version or should I sit on it until the next one?

/Magnus



---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Hi Magnus.

Cool!
I think it is good information.:-)
http://winpg.jp/~saito/pgAdmin/Block_info.png
I want it.
+1!

Regards,
Hiroshi Saito

----- Original Message -----
From: "Magnus Hagander" <magnus@hagander.net>
To: <pgadmin-hackers@postgresql.org>
Sent: Wednesday, August 29, 2007 7:06 PM
Subject: [pgadmin-hackers] Blocked by


> Hi!
>
> Attached patch implements a column in the server status view that shows if
> a transaction is blocked, and what process it's blocked by.
>
> Since we're very close to RC, I'm sending it past here before doing
> anything more. What do ppl think, are we ok with something like this for
> this version or should I sit on it until the next one?
>
> /Magnus
>
>


--------------------------------------------------------------------------------


>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Magnus Hagander wrote:
> Hi!
>
> Attached patch implements a column in the server status view that shows if
> a transaction is blocked, and what process it's blocked by.
>
> Since we're very close to RC, I'm sending it past here before doing
> anything more. What do ppl think, are we ok with something like this for
> this version or should I sit on it until the next one?

It's useful, but it does involve a string change very close to RC :-( I
need to fight the urge to commit it and stick to the rules I'm afraid -
I say no, not for this release.

As soon as we branch though, let's commit it. I hope we'll rewrite most
of that tool so it may not survive (we've been talking about having a
hierarchical view instead), but we should get it in in case we don't get
that.

/D

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On Wed, Aug 29, 2007 at 11:42:33AM +0100, Dave Page wrote:
> Magnus Hagander wrote:
> > Hi!
> >
> > Attached patch implements a column in the server status view that shows if
> > a transaction is blocked, and what process it's blocked by.
> >
> > Since we're very close to RC, I'm sending it past here before doing
> > anything more. What do ppl think, are we ok with something like this for
> > this version or should I sit on it until the next one?
>
> It's useful, but it does involve a string change very close to RC :-( I
> need to fight the urge to commit it and stick to the rules I'm afraid -
> I say no, not for this release.

Bummer, but I can't say it's a bad decision :-)

> As soon as we branch though, let's commit it. I hope we'll rewrite most
> of that tool so it may not survive (we've been talking about having a
> hierarchical view instead), but we should get it in in case we don't get
> that.

What's the plan for branching?

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Magnus Hagander wrote:
> On Wed, Aug 29, 2007 at 11:42:33AM +0100, Dave Page wrote:
>> Magnus Hagander wrote:
>>> Hi!
>>>
>>> Attached patch implements a column in the server status view that shows if
>>> a transaction is blocked, and what process it's blocked by.
>>>
>>> Since we're very close to RC, I'm sending it past here before doing
>>> anything more. What do ppl think, are we ok with something like this for
>>> this version or should I sit on it until the next one?
>> It's useful, but it does involve a string change very close to RC :-( I
>> need to fight the urge to commit it and stick to the rules I'm afraid -
>> I say no, not for this release.
>
> Bummer, but I can't say it's a bad decision :-)
>
>> As soon as we branch though, let's commit it. I hope we'll rewrite most
>> of that tool so it may not survive (we've been talking about having a
>> hierarchical view instead), but we should get it in in case we don't get
>> that.
>
> What's the plan for branching?

About 10 minutes after I bundle the release I imagine!

/D


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Magnus Hagander wrote:
> Hi!
>
> Attached patch implements a column in the server status view that shows if
> a transaction is blocked, and what process it's blocked by.

Thanks, patch applied.

/D

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate