[pgadmin-hackers] SVN Commit by hiroshi: r6587 - trunk/pgadmin3/docs/en_US
Author: hiroshi Date: 2007-08-29 10:08:38 +0100 (Wed, 29 Aug 2007) New Revision: 6587 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6587view=rev Log: private e-mail change. Modified: trunk/pgadmin3/docs/en_US/team.html trunk/pgadmin3/docs/en_US/translation_team.html ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[pgadmin-hackers] The difference in the icon pixel value of PostgreSQL and pgAdmin3.
Hi Dave. I have noticed the difference in beauty... It has the icon which PostgreSQL has by 48*48. But, pgAdmin3 is 32*32... http://winpg.jp/~saito/pgAdmin/pgAdmin_icon.png Left-hand side is the thing of PostgreSQL. Did pgAdmin3 have restrictions with some resources? Regards, Hiroshi Saito ---(end of broadcast)--- TIP 6: explain analyze is your friend
[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
Index: frm/frmStatus.cpp
===
--- frm/frmStatus.cpp (revision 6586)
+++ frm/frmStatus.cpp (working copy)
@@ -120,6 +120,7 @@
if (connection-BackendMinimumVersion(8, 3))
statusList-AddColumn(_(TX start), 50);
+ statusList-AddColumn(_(Blocked by), 35);
statusList-AddColumn(_(Query), 500);
lockList-AddColumn(wxT(PID), 50);
@@ -326,7 +327,7 @@
{
// Status
long row=0;
- pgSet *dataSet1=connection-ExecuteSet(wxT(SELECT * FROM
pg_stat_activity ORDER BY procpid));
+ pgSet *dataSet1=connection-ExecuteSet(wxT(SELECT *,(SELECT
min(pid) FROM pg_locks l1 WHERE GRANTED AND relation IN (SELECT relation FROM
pg_locks l2 WHERE l2.pid=procpid AND NOT granted)) AS blockedby FROM
pg_stat_activity ORDER BY procpid));
if (dataSet1)
{
statusList-Freeze();
@@ -378,6 +379,7 @@
if (connection-BackendMinimumVersion(8, 3))
statusList-SetItem(row, colpos++,
dataSet1-GetVal(wxT(txn_start)));
+ statusList-SetItem(row, colpos++,
dataSet1-GetVal(wxT(blockedby)));
statusList-SetItem(row, colpos, qry.Left(250));
row++;
}
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
[pgadmin-hackers] SVN Commit by dpage: r6588 - in trunk/pgadmin3/pgadmin: frm include/frm
Author: dpage Date: 2007-08-29 11:25:54 +0100 (Wed, 29 Aug 2007) New Revision: 6588 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6588view=rev Log: Restore the status of expanded child nodes when refreshing parts of the treeview. Modified: trunk/pgadmin3/pgadmin/frm/frmMain.cpp trunk/pgadmin3/pgadmin/include/frm/frmMain.h ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[pgadmin-hackers] SVN Commit by dpage: r6589 - trunk/pgadmin3/pgadmin/debugger
Author: dpage Date: 2007-08-29 11:33:31 +0100 (Wed, 29 Aug 2007) New Revision: 6589 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6589view=rev Log: Use a modal dialog for the debugger params. Not strictly necessary, but more consistent with other parts of pgAdmin. Modified: trunk/pgadmin3/pgadmin/debugger/dlgDirectDbg.cpp ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Blocked by
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 [EMAIL PROTECTED] 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
Re: [pgadmin-hackers] Blocked by
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
Re: [pgadmin-hackers] The difference in the icon pixel value of PostgreSQL and pgAdmin3.
Hiroshi Saito wrote: Hi Dave. I have noticed the difference in beauty... It has the icon which PostgreSQL has by 48*48. But, pgAdmin3 is 32*32... http://winpg.jp/~saito/pgAdmin/pgAdmin_icon.png Left-hand side is the thing of PostgreSQL. Yeah, I noticed that but didn't investigate yet. Did pgAdmin3 have restrictions with some resources? Don't think so - feel free to update it, but please ensure we have all the size/colour depth formats we currently have. Regards, Dave ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[pgadmin-hackers] SVN Commit by hiroshi: r6590 - trunk/pgadmin3/pgadmin/include/images
Author: hiroshi Date: 2007-08-29 12:09:21 +0100 (Wed, 29 Aug 2007) New Revision: 6590 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6590view=rev Log: It became somewhat beautiful.:-) Modified: trunk/pgadmin3/pgadmin/include/images/pgAdmin3.ico ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] Blocked by
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
Re: [pgadmin-hackers] Blocked by
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
[pgadmin-hackers] SVN Commit by dpage: r6591 - in trunk/pgadmin3/pgadmin: dlg frm schema
Author: dpage Date: 2007-08-29 14:43:50 +0100 (Wed, 29 Aug 2007) New Revision: 6591 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6591view=rev Log: Don't crash if the user selects a database that they cannot connect to, per Devrim Modified: trunk/pgadmin3/pgadmin/dlg/dlgProperty.cpp trunk/pgadmin3/pgadmin/frm/frmBackup.cpp trunk/pgadmin3/pgadmin/frm/frmBackupGlobals.cpp trunk/pgadmin3/pgadmin/frm/frmRestore.cpp trunk/pgadmin3/pgadmin/schema/pgDatabase.cpp ---(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
Re: [pgadmin-hackers] RC1 on Friday?
Devrim GÜNDÜZ wrote: Hi, On Tue, 2007-08-28 at 12:08 +0100, Dave Page wrote: I'm thinking we're about ready to release RC1 on Friday. Does anyone think we should have another beta first or disagree with the scheduling? Did you look at the bug that I told you on jabber? (Clicking template* crashes pgadmin3 on Linux.) Thanks, fixed in SVN. Regards, Dave ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[pgadmin-hackers] SVN Commit by dpage: r6592 - trunk/pgadmin3/pgadmin/frm
Author: dpage Date: 2007-08-29 15:22:53 +0100 (Wed, 29 Aug 2007) New Revision: 6592 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=6592view=rev Log: Fix the delete key in the edit grid scratch pad. Modified: trunk/pgadmin3/pgadmin/frm/frmEditGrid.cpp ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
