[pgadmin-hackers] v1.8.2 tagged and uploaded
I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! Thanks, Dave ---(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] v1.8.2 tagged and uploaded
Dave Page wrote: I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! It seems OK on Solaris . (Only too much underscores :-) Zdenek ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] v1.8.2 tagged and uploaded
Hi Dave, Dave Page wrote: I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! While working on my setowner patch, I've found a bug with the db restriction. I just applied a patch to fix this. I don't know if you want this patch to be part of 1.8.2, but I thought I should let you know about it. (I've put 1.8.3 in the CHANGELOG file.) -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] v1.8.2 tagged and uploaded
On Feb 1, 2008 10:11 PM, Guillaume Lelarge [EMAIL PROTECTED] wrote: Hi Dave, Dave Page wrote: I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! While working on my setowner patch, I've found a bug with the db restriction. I just applied a patch to fix this. I don't know if you want this patch to be part of 1.8.2, but I thought I should let you know about it. (I've put 1.8.3 in the CHANGELOG file.) No, it can wait for 1.8.3. I assume it's been there a while. Thanks, Dave ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] v1.8.2 tagged and uploaded
Dave Page wrote: On Feb 1, 2008 10:11 PM, Guillaume Lelarge [EMAIL PROTECTED] wrote: Dave Page wrote: I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! While working on my setowner patch, I've found a bug with the db restriction. I just applied a patch to fix this. I don't know if you want this patch to be part of 1.8.2, but I thought I should let you know about it. (I've put 1.8.3 in the CHANGELOG file.) No, it can wait for 1.8.3. I assume it's been there a while. Yes, I think you're right. Nobody complains about this. -- 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] v1.8.2 tagged and uploaded
Hi. Great! FreeBSD OpenSuSE is Done now:-) Regards, Hiroshi Saito Hi, On Fri, 2008-02-01 at 12:17 +, Dave Page wrote: I've uploaded 1.8.2 in the normal source, win32, slackware and osx formats to http://developer.pgadmin.org/ftp/release/v1.8.2/. Please give them a once-over and report any major issues before I announce!! RHEL 4,5 and Fedora 7,8 packages are now available in PGDG RPM repository: http://yum.pgsqlrpms.org . I also submitted them to Fedora for build, they will appear shortly. Regards, -- Devrim GUNDUZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.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
