[pgadmin-hackers] RC2 needed?
Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings /D ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [pgadmin-hackers] RC2 needed?
Dave Page a écrit : Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings I don't think we need one. Even Erwin didn't complain for a month or so :) Regards. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] RC2 needed?
Guillaume Lelarge wrote: Even Erwin didn't complain for a month or so :) :-D /D ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] RC2 needed?
On Mon, Oct 15, 2007 at 01:55:34PM +0100, Dave Page wrote: Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings The greenplum query shouds like the one that would reallyi need a bit larger testing. Meaning it has to run against a bunch of different pg versinos. But if you've done that, then I think we're fine. //Magnus ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] RC2 needed?
Magnus Hagander wrote: On Mon, Oct 15, 2007 at 01:55:34PM +0100, Dave Page wrote: Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings The greenplum query shouds like the one that would reallyi need a bit larger testing. Meaning it has to run against a bunch of different pg versinos. But if you've done that, then I think we're fine. I've run it against 8.2 and 8.3, but it's not a hugely complex query. Anyone running SVN-trunk got any older installs running? /D ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] RC2 needed?
Dave Page a écrit : Magnus Hagander wrote: On Mon, Oct 15, 2007 at 01:55:34PM +0100, Dave Page wrote: Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings The greenplum query shouds like the one that would reallyi need a bit larger testing. Meaning it has to run against a bunch of different pg versinos. But if you've done that, then I think we're fine. I've run it against 8.2 and 8.3, but it's not a hugely complex query. Anyone running SVN-trunk got any older installs running? I have 7.4-cvs and 8.1-cvs... I'll try on those. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(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] RC2 needed?
Guillaume Lelarge wrote: Dave Page a écrit : Magnus Hagander wrote: On Mon, Oct 15, 2007 at 01:55:34PM +0100, Dave Page wrote: Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings The greenplum query shouds like the one that would reallyi need a bit larger testing. Meaning it has to run against a bunch of different pg versinos. But if you've done that, then I think we're fine. I've run it against 8.2 and 8.3, but it's not a hugely complex query. Anyone running SVN-trunk got any older installs running? I have 7.4-cvs and 8.1-cvs... I'll try on those. Thanks. Just tried 7.3 here but it won't build on my Mac :-( /D ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [pgadmin-hackers] RC2 needed?
Dave Page wrote: Guillaume Lelarge wrote: Dave Page a écrit : Magnus Hagander wrote: On Mon, Oct 15, 2007 at 01:55:34PM +0100, Dave Page wrote: Does anyone think we need an RC2 release? The list of changes since RC1 is currently (excluding translations etc): - Icon update - Guard against checking the server version if we're not connected. - Check the PostgreSQL release before adding tablespace query, per reports from Albin Blaschka and Ariel R. Giomi. - Fix the tablespace issue on index and indexconstraint. - Avoid using a correlated subquery that Greenplum doesn't support, per report from Jon Roberts. - Prevent characters being incorrectly stripped from foreign key column names, per Alexander Kirpa - Cleanup some compiler warnings The greenplum query shouds like the one that would reallyi need a bit larger testing. Meaning it has to run against a bunch of different pg versinos. But if you've done that, then I think we're fine. I've run it against 8.2 and 8.3, but it's not a hugely complex query. Anyone running SVN-trunk got any older installs running? I have 7.4-cvs and 8.1-cvs... I'll try on those. Thanks. Just tried 7.3 here but it won't build on my Mac :-( I can try 7.3, but you'll have to tell me what to test. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(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] RC2 needed?
Heikki Linnakangas wrote: Thanks. Just tried 7.3 here but it won't build on my Mac :-( I can try 7.3, but you'll have to tell me what to test. Thanks Heikki. - Create a postgres database (to avoid cluttering template1) - Run pgagent.sql (should be in xtra/pgagent in the pgadmin source tree) in that database. - Start a build of pgAdmin SVN-trunk. - Add a new server, using the postgres database as the maintenance db in the server dialogue. - Connect to the server and under the server node alongside databases and roles etc. you should see a 'Jobs' node. You shouldn't have got any SQL errors at this point! - Right-click Jobs, and try adding a simple job with a step and a schedule. - Try refreshing the Jobs node a couple of times. /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] RC2 needed?
Guillaume Lelarge wrote: First, you'll need to install some stuff : * create a postgres database ; * change the pgagent.sql file (there's a dollar quote function that disallow it to be used where pre-8.0 release) ; * launch pgagent like this : pgagent hostaddr=IP_ADDR dbname=postgres There's no need to run pgagent itself. All the changed code is in pgAdmin. Then * launch pgAdmin * create a job (http://www.pgadmin.org/docs/dev/pgagent-jobs.html) To be honest, I don't find the pgagent interface when I use my 7.4 and 8.1 cluster. This will take more time than I first thought. Make sure you run the SQL file in the maintenance DB. /D ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] RC2 needed?
Dave Page wrote: Heikki Linnakangas wrote: Thanks. Just tried 7.3 here but it won't build on my Mac :-( I can try 7.3, but you'll have to tell me what to test. Thanks Heikki. - Create a postgres database (to avoid cluttering template1) - Run pgagent.sql (should be in xtra/pgagent in the pgadmin source tree) in that database. That step failed: ERROR: Function array_upper(boolean[], integer) does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(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
Re: [pgadmin-hackers] RC2 needed?
Dave Page a écrit : Guillaume Lelarge wrote: First, you'll need to install some stuff : * create a postgres database ; * change the pgagent.sql file (there's a dollar quote function that disallow it to be used where pre-8.0 release) ; * launch pgagent like this : pgagent hostaddr=IP_ADDR dbname=postgres There's no need to run pgagent itself. All the changed code is in pgAdmin. Then * launch pgAdmin * create a job (http://www.pgadmin.org/docs/dev/pgagent-jobs.html) To be honest, I don't find the pgagent interface when I use my 7.4 and 8.1 cluster. This will take more time than I first thought. Make sure you run the SQL file in the maintenance DB. I found the issue with your last email. The maintenance DB was still template1. I can add a job but, even after a refresh, I can't see it. I only gave a name to my job and click OK. So, it seems the SELECT DISTINCT returns nothing. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] RC2 needed?
Guillaume Lelarge a écrit : Dave Page a écrit : Guillaume Lelarge wrote: First, you'll need to install some stuff : * create a postgres database ; * change the pgagent.sql file (there's a dollar quote function that disallow it to be used where pre-8.0 release) ; * launch pgagent like this : pgagent hostaddr=IP_ADDR dbname=postgres There's no need to run pgagent itself. All the changed code is in pgAdmin. Then * launch pgAdmin * create a job (http://www.pgadmin.org/docs/dev/pgagent-jobs.html) To be honest, I don't find the pgagent interface when I use my 7.4 and 8.1 cluster. This will take more time than I first thought. Make sure you run the SQL file in the maintenance DB. I found the issue with your last email. The maintenance DB was still template1. I can add a job but, even after a refresh, I can't see it. I only gave a name to my job and click OK. So, it seems the SELECT DISTINCT returns nothing. I forgot to mention that this test was done using PostgreSQL 8.1 (latest CVS checkout). -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] RC2 needed?
Heikki Linnakangas wrote: Dave Page wrote: Heikki Linnakangas wrote: Thanks. Just tried 7.3 here but it won't build on my Mac :-( I can try 7.3, but you'll have to tell me what to test. Thanks Heikki. - Create a postgres database (to avoid cluttering template1) - Run pgagent.sql (should be in xtra/pgagent in the pgadmin source tree) in that database. That step failed: ERROR: Function array_upper(boolean[], integer) does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts :-) That shows how many folks are using pgagent with 7.3 - that's been there since at least April 2005! I'm inclined to just say we don't support pgAgent on 7.3. Thanks for testing. /D ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] RC2 needed?
Guillaume Lelarge wrote: Dave Page a écrit : Guillaume Lelarge wrote: First, you'll need to install some stuff : * create a postgres database ; * change the pgagent.sql file (there's a dollar quote function that disallow it to be used where pre-8.0 release) ; * launch pgagent like this : pgagent hostaddr=IP_ADDR dbname=postgres There's no need to run pgagent itself. All the changed code is in pgAdmin. Then * launch pgAdmin * create a job (http://www.pgadmin.org/docs/dev/pgagent-jobs.html) To be honest, I don't find the pgagent interface when I use my 7.4 and 8.1 cluster. This will take more time than I first thought. Make sure you run the SQL file in the maintenance DB. I found the issue with your last email. The maintenance DB was still template1. I can add a job but, even after a refresh, I can't see it. I only gave a name to my job and click OK. So, it seems the SELECT DISTINCT returns nothing. Rats - could have sworn I tested that but I must have done something stupid. Please try with SVN trunk - it should be OK now. /D ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] RC2 needed?
Dave Page a écrit : Guillaume Lelarge wrote: Dave Page a écrit : Guillaume Lelarge wrote: First, you'll need to install some stuff : * create a postgres database ; * change the pgagent.sql file (there's a dollar quote function that disallow it to be used where pre-8.0 release) ; * launch pgagent like this : pgagent hostaddr=IP_ADDR dbname=postgres There's no need to run pgagent itself. All the changed code is in pgAdmin. Then * launch pgAdmin * create a job (http://www.pgadmin.org/docs/dev/pgagent-jobs.html) To be honest, I don't find the pgagent interface when I use my 7.4 and 8.1 cluster. This will take more time than I first thought. Make sure you run the SQL file in the maintenance DB. I found the issue with your last email. The maintenance DB was still template1. I can add a job but, even after a refresh, I can't see it. I only gave a name to my job and click OK. So, it seems the SELECT DISTINCT returns nothing. Rats - could have sworn I tested that but I must have done something stupid. Please try with SVN trunk - it should be OK now. Works on 7.4 and 8.1. I'll commit my fix on the dollar quoting stuff if you don't mind. It'll allow 7.4 users to use pgAgent. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgadmin-hackers] RC2 needed?
Dave Page wrote: Heikki Linnakangas wrote: Dave Page wrote: Heikki Linnakangas wrote: Thanks. Just tried 7.3 here but it won't build on my Mac :-( I can try 7.3, but you'll have to tell me what to test. Thanks Heikki. - Create a postgres database (to avoid cluttering template1) - Run pgagent.sql (should be in xtra/pgagent in the pgadmin source tree) in that database. That step failed: ERROR: Function array_upper(boolean[], integer) does not exist Unable to identify a function that satisfies the given argument types You may need to add explicit typecasts :-) That shows how many folks are using pgagent with 7.3 - that's been there since at least April 2005! I'm inclined to just say we don't support pgAgent on 7.3. Agreed, in case you actually wanted a second opinion on that. //Magnus ---(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
Re: [pgadmin-hackers] RC2 needed
Dave Page wrote: OK, anything else to go in? Nothing I'm aware of. Any other system schema change I didn't notice? I can *possibly* do one tomorrow, following that, I'm taking 2 weeks off work having now finished at Uni (yay!) so will probably be working on pgAdmin etc. in the evenings only (which won't stop me doing an RC. I'd like to filter the translations this time around as well. Did we decide on a criteria for inclusion yet? No. How is this handled in pgsql? Should we drop 10 languages we previously supported? Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] RC2 needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 12 Nov 2004, Andreas Pflug wrote: I'd like to filter the translations this time around as well. Did we decide on a criteria for inclusion yet? No. How is this handled in pgsql? Should we drop 10 languages we previously supported? %99 might be a sub-limit for translations :-D (Turkish is 99% heh heh heh) - -- Devrim GUNDUZ devrim~gunduz.orgdevrim.gunduz~linux.org.tr http://www.tdmsoft.com http://www.gunduz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBlJCvtl86P3SPfQ4RAsbyAKDYPe5E0lCL3uFqfxk7+Dxtk+6UKwCgkbg5 Sa30ZYzMGOAogH0AJZPQkzI= =B7ym -END PGP SIGNATURE- ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] RC2 needed
-Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 12 November 2004 10:09 To: Dave Page Cc: pgadmin-hackers Subject: Re: [pgadmin-hackers] RC2 needed Dave Page wrote: OK, anything else to go in? Nothing I'm aware of. Any other system schema change I didn't notice? Don't think so. I didn't notice that one :-( (which I think is odd considering the normal amount of chatter regarding initdb's during beta). Still, I have been somewhat distracted these last couple of weeks. I can *possibly* do one tomorrow, following that, I'm taking 2 weeks off work having now finished at Uni (yay!) so will probably be working on pgAdmin etc. in the evenings only (which won't stop me doing an RC. I'd like to filter the translations this time around as well. Did we decide on a criteria for inclusion yet? No. How is this handled in pgsql? Should we drop 10 languages we previously supported? Don't know, and perhaps, yes. It has been noted to me a couple of times in the past that partial translations just look messy and unprofessional, so maybe we drop any below, say, 90%, and add a note to the helpfile telling users how they can get the partials if they want, and how they can help improve them? I have already moved the 'clearly unmaintained' ones to the pending section on the website, and merged the vacant section with it as you may have noticed. I think I have also fixed the caching problem btw - translation updates should now be shown within 15 minutes on www and developer. Anyway, the new organisation leaves only one translation in the published table at below 90% (Hungarian). Interestingly, one unmaintained one (Chinese Traditional) is actually at 91%... Did Chih-Hsin Lee 'resign'? Regards, Dave ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] RC2 needed
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 12 November 2004 10:09 To: Dave Page Cc: pgadmin-hackers Subject: Re: [pgadmin-hackers] RC2 needed Dave Page wrote: OK, anything else to go in? Nothing I'm aware of. Any other system schema change I didn't notice? Don't think so. I didn't notice that one :-( (which I think is odd considering the normal amount of chatter regarding initdb's during beta). Still, I have been somewhat distracted these last couple of weeks. I can *possibly* do one tomorrow, following that, I'm taking 2 weeks off work having now finished at Uni (yay!) so will probably be working on pgAdmin etc. in the evenings only (which won't stop me doing an RC. I'd like to filter the translations this time around as well. Did we decide on a criteria for inclusion yet? No. How is this handled in pgsql? Should we drop 10 languages we previously supported? Don't know, and perhaps, yes. It has been noted to me a couple of times in the past that partial translations just look messy and unprofessional, so maybe we drop any below, say, 90%, and add a note to the helpfile telling users how they can get the partials if they want, and how they can help improve them? I have already moved the 'clearly unmaintained' ones to the pending section on the website, and merged the vacant section with it as you may have noticed. I think I have also fixed the caching problem btw - translation updates should now be shown within 15 minutes on www and developer. Anyway, the new organisation leaves only one translation in the published table at below 90% (Hungarian). Interestingly, one unmaintained one (Chinese Traditional) is actually at 91%... Did Chih-Hsin Lee 'resign'? The previous version did reflect the feedback status on resigned translators. lookup ver='prev'Arabic, Swedish and Chinese (trad) gave feedback that they couldn't proceed/lookup I don't see a reason to keep those 0 % translations after one year of zero result. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] RC2 needed
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Pflug Sent: 10 November 2004 18:42 To: pgadmin-hackers Subject: [pgadmin-hackers] RC2 needed Seems we should roll a second RC quite soon, because RC1 has the comboboxes messed up in gtk (thanks to me), and pgsql just changed the system schema in a way that stops pgsql from working. Hopefully, we don't have more of those last minute schema changes... OK, anything else to go in? I can *possibly* do one tomorrow, following that, I'm taking 2 weeks off work having now finished at Uni (yay!) so will probably be working on pgAdmin etc. in the evenings only (which won't stop me doing an RC. I'd like to filter the translations this time around as well. Did we decide on a criteria for inclusion yet? Regards, Dave ---(end of broadcast)--- TIP 8: explain analyze is your friend
