Re: [BUGS] BUG #8498: pg_trgm is missing from windows edb package
On 5 Oct 2013, at 13:21, Michael Paquier michael.paqu...@gmail.com wrote: On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation l...@pcorp.us wrote: Disregard my bug complaint. Stupid user error. Btw, the next time you find an error with this installer, you should not use this mailing list for this purpose but contact directly EDB as this installer is maintained by them and not by community. EDB (and many of it's staff) are part of the community, just as various other companies and their staff who contribute in other ways are. Further, the PostgreSQL installers are offered as 'official' releases on the community website, so it is quite reasonable for users to report bugs here. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8288: 9.3.0Beta2 - Windows Installer bug #7738 still open
On Tue, Jul 9, 2013 at 1:44 PM, tga...@wolfsysteme.de wrote: The following bug has been logged on the website: Bug reference: 8288 Logged by: Thomas Gauss Email address: tga...@wolfsysteme.de PostgreSQL version: Unsupported/Unknown Operating system: Windows 7 64bit Description: Having data directory on drive d:\database\data-9.3 it takes about 45 minutes to initialise cluster. Most of the time icacls is run by the installer, seems like bug#7738 is still active in 9.3.0b2's installer. iirc, we eventually came to the conclusion that in some (unknown) circumstances, icacls will recursively examine ACLs, even though it's not updating them. We're currently looking into alternative ways to ensure the permissions needed to write to the data directory are correct. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Installer: Spurious service account ... not removed on uninstall
On Mon, Jul 1, 2013 at 12:51 AM, Craig Ringer cr...@2ndquadrant.com wrote: Hi folks A Stack Overflow user noticed that the EDB installer for PostgreSQL emits the message: The data directory (bla bla) and service user account (NT AUTHORITY\NetworkService) have not been removed when 9.2 is uninstalled. They were quite confused by this. It occurs to me that if the standard NetworkService account is used, it'd be good to suppress the user account not removed part of the message entirely. http://stackoverflow.com/q/17394116/398670 Thanks Craig. Sandeep, can you please modify the message so the part about the user account is omitted if it's NetworkService? Please do so for 9.2 and later. Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Inconsistent PL error handling
Whilst working on a build issue with pl/python, I noticed an inconsistency in the way the server reacts to attempts to use PLs for which the interpreter doesn't exist. Not sure how feasible it would be to fix this, but the Python case doesn't seem ideal: psql.bin (9.3beta1) Type help for help. postgres=# CREATE LANGUAGE plperl; ERROR: could not load library /opt/PostgreSQL/9.3/lib/postgresql/plperl.so: libperl.so: cannot open shared object file: No such file or directory postgres=# CREATE LANGUAGE plpython3u; CREATE LANGUAGE postgres=# CREATE FUNCTION pyversion() RETURNS text AS $$ import sys return sys.version $$ LANGUAGE 'plpython3u'; The connection to the server was lost. Attempting reset: Failed. ! The server was compiled with both Perl and Python support using the ActiveState packages on 64 bit Linux on the build machine, but the runtime machine had neither installed (as would often be the case for installer packages). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7983: Problem with pgAgent.
Hi On Fri, Mar 22, 2013 at 2:23 PM, Marcelo Matheus marcelo_math...@oi.com.br wrote: Good afternoon, Dave. The output of led mount brings the following about the / tmp: /dev/mapper/vg_vmpjebdh2-LogVol01 on /tmp type ext4 (rw,noexec,nosuid,nodev,noat ime) That's likely the issue then - you need to mount /tmp without the noexec option for pgAgent to be able to work. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7984: passwordcheck module not enforced in PGAdmin GUI
On Fri, Mar 22, 2013 at 8:23 PM, pmahal...@intertrust.com wrote: The following bug has been logged on the website: Bug reference: 7984 Logged by: passwordcheck module is not enforced by PGAdmin GUI Email address: pmahal...@intertrust.com PostgreSQL version: 9.1.0 Operating system: Windows Description: Hi, We've enabled the Postgres passwordcheck modules by following instructions as mentioned on http://www.postgresql.org/docs/9.1/static/passwordcheck.html Did you read the large Caution box on that page? Now we find that this password strength check is only enforced in command line mode. PGAdmin still accepts the weak password. Please fix. We're not going to modify pgAdmin to send plain-text passwords over the wire. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7983: Problem with pgAgent.
On Thu, Mar 21, 2013 at 8:12 PM, marcelo_math...@oi.com.br wrote: The following bug has been logged on the website: Bug reference: 7983 Logged by: Marcelo Nunes Email address: marcelo_math...@oi.com.br PostgreSQL version: 9.1.4 Operating system: Linux Red Hat 6 Description: Hello, good afternoon. When trying to run a batch in pgAgent the following error occurs. DEBUG: Checking for jobs to run DEBUG: Sleeping... sh: /tmp/pga_GvQxqM/5_9.scr: Permission denied DEBUG: Clearing inactive connections DEBUG: Connection stats: total - 1, free - 0, deleted - 0 DEBUG: Checking for jobs to run DEBUG: Sleeping... I have no idea what may be happening. The / tmp is allowed for everyone. Is /tmp mounted with the noexec option? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7983: Problem with pgAgent.
On Fri, Mar 22, 2013 at 11:58 AM, Marcelo Matheus marcelo_math...@oi.com.br wrote: Hello, Dave. The pemissões of / tmp are: [root@vmpjebdh /]# ls -ld /tmp drwxrwxrwt. 18 root root 4096 Mar 22 12:29 /tmp Right, but is it mounted with noexec? Look at the output from the mount command. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7851: Installer crash with message: An error occured executing the Microsoft VC++ runtimeinstaller
On Wed, Feb 6, 2013 at 3:03 PM, Ivano Luberti lube...@archicoop.it wrote: Thanks Dave, I have followe your instructions and the result is really weird. The script doesn't run and error message is that VBScript interpreter cannot be found. At the same time .vbs files are recognized as associated with WScript.exe OK, so there definitely is something messed up with your script interpreter. I believe you said you already tried re-registering vbscript.dll, so something else seems to be preventing things from working. I wonder if these would help in tracking down and fixing the issue? http://www.sevenforums.com/windows-updates-activation/196011-cscript-error-cant-find-script-engine-vbscript-alternate-solution.html http://social.microsoft.com/Forums/eu/genuinevista/thread/1b7332ba-d1f7-455f-b523-1dc45bc2b939 -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Bug #7728
Hi On Wed, Feb 6, 2013 at 12:39 AM, William Goh wgoh9...@gmail.com wrote: Dear EnterpriseDB, I am trying to install PostgreSQL 9.2.2 on my mac 10.5.8. However, I have encountered the same error posted in this thread: http://www.postgresql.org/message-id/CA+RD+ki0F9m5hOo-pxCVKoFO9AqHfPxVRthF49b4pBn=hzt...@mail.gmail.com I was wondering if there is any way to get around this error and successfully install postgresql on my computer. You can either use the 9.1 installer which should work on OS X 10.5, or use an alternate distribution, such as MacPorts, which will compile the server for your version of OS X. Unfortunately it's hard for us to build releases that continue to support older versions of OS X, as when we buy new build machines they won't run older versions of OS X, and the modern versions of OS X don't support compiling code for much older versions (they only supplied SDKs for 10.7 and 10.8 with the last version of XCode I got for example). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] A bug in documentation for the Query Tool PostgreSQL Version 9.2.2, Win x86-64
Thanks - I've committed a fix for this. On Wed, Feb 6, 2013 at 3:15 PM, Jozef Hlavaty elfish...@yahoo.com wrote: Dear Sir/Madam, Firstly let me congratulate all responsible for delivering us such a fine piece of software. I take my hat off to you all. I've donwloaded and installed PostgreSQL Version 9.2.2, Windows x86-64bit version ad would like to report a bug in documentation for the Query Tool. The path to the page which I believe contains the bug: mk:@MSITStore :C:\Program%20Files\PostgreSQL\9.2\pgAdmin%20III\docs\en_US\pgadmin3.chm::/query.html In the section with code formatting commands the last two lines read: Shift the selected text to upper case by pressing Control+Shift+U. Shift the selected text to lower case by pressing Control+U. In fact they the shortcuts should be swapped: Shift the selected text to upper case by pressing Control+U. Shift the selected text to lower case by pressing Control+Shift+U. Thanks and Regards, Jozef -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #7851: Installer crash with message: An error occured executing the Microsoft VC++ runtimeinstaller
On Wed, Feb 6, 2013 at 5:07 PM, Ivano Luberti lube...@archicoop.it wrote: Yes the problem is exaclty that: I had MCAfee installed when the laptop was shipped. I promptly uninstalled it but it seems there are still traces of it. Oh, urgh. Unfortunately the fix doesn't work because it seems the registry key is protected even form administrator user modifications. Even if you run regedit from a command prompt started as Administrator? I'm searching a workaround to update the registry. Thanks for now: you are doing a great job, Dave. You're welcome - glad to be of help. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7851: Installer crash with message: An error occured executing the Microsoft VC++ runtimeinstaller
On Wed, Feb 6, 2013 at 5:30 PM, Ivano Luberti lube...@archicoop.it wrote: Found the solution for modifyng the registry key here http://www.mydigitallife.info/grant-read-write-full-control-permissions-on-registry-keys-fix-cannot-import-and-access-denied-error-in-regedit/ Oh, OK - so you didn't have permissions to edit that section of the registry, but you can modify the ACL? Cool. So, does cscript (and thus hopefully the installer) work now? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] SOLVED: BUG #7851: Installer crash with message: An error occured executing the Microsoft VC++ runtimeinstaller
On Wed, Feb 6, 2013 at 8:36 PM, Ivano Luberti lube...@archicoop.it wrote:
With a little bit of more drama.
The good news is that the 9.2 installer has been able to successfully
complete installation.
The bad news is that 8.4.15 installer keep failing and with the same message
error.
I searched the registry again with regedit and found another occurence of
the same registry key under
HKEY_CLASSES_ROOT\Wow6432node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
still linked to McAfee.
I had to change ownership also in this case to modify its value
But now 8.4.15 can run like an horse at Kentucky Derby
I believe that the last issue was due to the fact that 9.2 installer is a
64bit software while 8.4.15 is a 32bit application.
Excellent news! So the moral of the story is: Avoid using any computer
that has had McAfee software anywhere near it.
Dave, thanks again for your help.
You're welcome.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7851: Installer crash with message: An error occured executing the Microsoft VC++ runtimeinstaller
On Tue, Feb 5, 2013 at 10:45 AM, lube...@archicoop.it wrote: The following bug has been logged on the website: Bug reference: 7851 Logged by: ivano luberti Email address: lube...@archicoop.it PostgreSQL version: 8.4.15 Operating system: Windows 7 Home Premium 64 bits Description: I know this is probalby a duplicate of bug BUG #7526 but I don't know how to update it with new information so I submit a new one. The same error message raised with 8.3.22 and 9.2.2. But I was then able to install 8.3.22 using the pginstaller found at http://www.postgresql.org/ftp/binary/v8.3.22/win32/ Ok this the new piece of information. Unfortunately pginstaller is available only for 8.3.x. So I'm stuck since I need 8.4.x If this is a new installation, you should really use 9.2. 8.4 will go out of support in about a year. Executing cscript //NoLogo C:\Users\luberti\AppData\Local\Temp\postgresql_installer\installruntimes.vbs C:\Users\luberti\AppData\Local\Temp\postgresql_installer\vcredist_x86.exe Script exit code: 1 Script output: Errore CScript: Impossibile trovare l'interprete di script VBScript per lo script C:\Users\luberti\AppData\Local\Temp\postgresql_installer\installruntimes.vbs. Script stderr: Program ended with an error exit code An error occured executing the Microsoft VC++ runtime installer. You're suffering from the problem described here: http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows#The_installer_exits_with_a_runtime_installation_error.3F. The error comes usually because either the script interpretor isn't registered or the TEMP dir is unwriteable (both of which you said you've checked), or sometimes because the .vbs file extension is registered incorrectly. You can check how the filetype is registered like this: C:\assoc .vbs .vbs=VBSFile C:\ftype VBSFile VBSFile=%SystemRoot%\System32\WScript.exe %1 %* (it should look like that) -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7843: Incorrect using icacls
On Friday, February 1, 2013, wrote: The following bug has been logged on the website: Bug reference: 7843 Logged by: Andrey Email address: quiver...@gmail.com javascript:; PostgreSQL version: 9.2.2 Operating system: Windows 7 x64 Description: When i try to install postgresql-9.2.2-1-windows-x64.exe, it ask aboute DB files path. I have chosen d:\Server\DB\ then installer runs but file: @ECHO OFF icacls D:\ /grant NT AUTHORITY\NetworkService:(NP)(RX) C:\Temp\rad9B244.tmp 21 EXIT /B %ERRORLEVEL% It is incorrect. I believe that cacls should be run only on specified path (d:\Server\DB\). Besides this path have full access for Everyone and Administrators. This is intentional - it traverses back up the path and makes sure that the service account user has read and execute permissions on each directory up to and including the root. Otherwise, it may not be able to actually write to the data directory, even if it has permission on that directory. It's a somewhat brute-force approach that I hope to improve by 9.3, maybe earlier, but it does prevent failures in some environments. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #7781: pgagent incorrect installation
On Mon, Jan 7, 2013 at 6:47 AM, Aleksander Shniperson alex.shniper...@gmail.com wrote: There is no install-pgagent.log file. Anyway i try to sudo find no result. 07.01.2013, в 9:19, Sandeep Thakkar написал(а): The ini file clearly says that the pgAgent has been installed in /Library/pgAgent. Can you please share install-pgagent.log from your system temp (/tmp)? [pgAgent] Description=pgAgent is a job scheduler for PostgreSQL which may be managed using pgAdmin. InstallationDirectory=/Library/pgAgent PGDATABASE=postgres PGHOST=localhost PGPORT=5432 PGUSER=postgres ServiceManager=postgres UpgradeMode=0 Version=3.2.1-1 Sandeep is correct - it looks very much like the original installation has been manually, but partially removed. I would remove the pgAgent section from /etc/postgres-reg.ini, and try installing 3.3.0 again. That will make the installer run in installation mode instead of upgrade mode. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7781: pgagent incorrect installation
On Thu, Jan 3, 2013 at 8:44 AM, alex.shniper...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 7781 Logged by: Alexander Shniperson Email address: alex.shniper...@gmail.com PostgreSQL version: 9.1.7 Operating system: osx lion 10.7.5 Description: Hi. Just installed last PostgreSQL 9.1.7 and installed pgAgent from Application builder, but when i run pgAdmin no Jobs at all and even more in console i have error com.apple.launchd: (com.edb.launchd.pgagent[55389]) posix_spawn(/Library/pgAgent/bin/pgagent, ...): No such file or directory fix it please, thanks. Please try the 3.3.0 update that was just released. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7781: pgagent incorrect installation
On Fri, Jan 4, 2013 at 3:15 PM, Aleksander Shniperson alex.shniper...@gmail.com wrote: I can't do that, every time i run ApplicationBuilder i see new version 3.3.0, then i chose next next next and nothing changes. Define nothing changes please. Do you mean it doesn't fix the problem? It works fine for me here: raptor:server dpage$ ps -ef |grep pgagent 502 87069 1 0 3:22pm ?? 0:00.08 /Library/pgAgent/bin/pgagent -f -l1 -s /var/log/pgagent.log host=localhost port=5434 dbname=postgres user=postgres 501 87102 87078 0 3:24pm ttys0040:00.00 grep pgagent raptor:server dpage$ sudo launchctl unload /Library/LaunchDaemons/com.edb.launchd.pgagent.plist raptor:server dpage$ ps -ef |grep pgagent 501 87108 87078 0 3:24pm ttys0040:00.00 grep pgagent raptor:server dpage$ sudo launchctl load /Library/LaunchDaemons/com.edb.launchd.pgagent.plist raptor:server dpage$ ps -ef |grep pgagent 502 87114 1 0 3:24pm ?? 0:00.04 /Library/pgAgent/bin/pgagent -f -l1 -s /var/log/pgagent.log host=localhost port=5434 dbname=postgres user=postgres 501 87117 87078 0 3:24pm ttys0040:00.00 grep pgagent -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7781: pgagent incorrect installation
On Fri, Jan 4, 2013 at 3:43 PM, Aleksander Shniperson alex.shniper...@gmail.com wrote: Sorry. It does not fix the problem. /Library/pgAgent path not exists. So where did you install it if that path doesn't exist? My suggestion would be to figure that out, then uninstall the old version before starting over with the new - e.g. sudo open /Library/pgAgent/uninstall-pgagent.app -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7781: pgagent incorrect installation
e.g. means for example. Once you've figured out where it is installed, you should substitute the correct path into the example I gave. On Fri, Jan 4, 2013 at 4:28 PM, Aleksander Shniperson alex.shniper...@gmail.com wrote: LoL path /Library/pgAgent does not exists, i can't run uninstall 04.01.2013, в 20:18, Dave Page написал(а): On Fri, Jan 4, 2013 at 3:43 PM, Aleksander Shniperson alex.shniper...@gmail.com wrote: Sorry. It does not fix the problem. /Library/pgAgent path not exists. So where did you install it if that path doesn't exist? My suggestion would be to figure that out, then uninstall the old version before starting over with the new - e.g. sudo open /Library/pgAgent/uninstall-pgagent.app -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7781: pgagent incorrect installation
On Fri, Jan 4, 2013 at 4:35 PM, Aleksander Shniperson alex.shniper...@gmail.com wrote: sudo find / -name uninstall-pgagent.app gives no result. What's in /etc/postgres-reg.ini? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7740: Installation cannot fine msi file
Hi Sandeep Note that this report is regarding an MSI installer, not one of the EDB ones. I suspect the problem is related to the fact that pgFoundry has had numerous problems over the last week or two, as well as the fact that the admins are in the process of upgrading GForge and splitting into two servers. That's broken a few things recently (which have been fixed pretty quickly once noticed). On Mon, Dec 10, 2012 at 6:01 AM, Sandeep Thakkar sandeep.thak...@enterprisedb.com wrote: Hi Do you see this on Win7 32bit or 64bit? Can you please send the installation logs from your temp folder? On Sat, Dec 8, 2012 at 4:35 AM, al_chir...@hotmail.com wrote: The following bug has been logged on the website: Bug reference: 7740 Logged by: Al Chirico Email address: al_chir...@hotmail.com PostgreSQL version: 9.2.2 Operating system: Win 7 Pro Description: I am getting the following Stack Builder error message during installation: Failed to open http://ftp.postgresql.org/pub/projects/pgFoundry/stackbuilder/PgOleDB-1.0.0.20.msi; -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Sandeep Thakkar Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91.20.30589514 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7628: Installation of PostgreSQL 9.2.1 on Windows 7 may take too long
On Thu, Nov 1, 2012 at 5:41 AM, Craig Ringer ring...@ringerc.id.au wrote: On 11/01/2012 01:23 PM, Sandeep Thakkar wrote: Thanks George. I have fixed the typo in initcluster.vbs on all affected branches. Out of interest, how long has that typo been there? Could this be the cause of *all* the various and persistent issues we've had with icacls.exe running for ages on some systems? Or have there been previous problems detected and fixed too? No, not all. It was introduced in a previous fix for the issue in October 2011. Given the typo, I think the original fix was partially effective (hence the occasional reports we still get). With any luck, this will knock them on the head altogether. I'm kinda annoyed we never spotted this, given the number of people that have spent time reviewing and double-checking that code (myself included). I guess these things happen sometimes no matter how thorough you are :-( -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7613: INTIDB
On Thursday, October 18, 2012, wrote: The following bug has been logged on the website: Bug reference: 7613 Logged by: Henrique Silva Email address: henrique.assesso...@hotmail.com javascript:; PostgreSQL version: 8.3.20 Operating system: Windows Seven Description: Falha ao executar o Initdb.1! 8.3.x has never been supported on Windows 7. Try 9.2. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #7601: Installation of PostGresql at c:\Progam files folder does not create right permission on data folder
Hang on... please see if you can reproduce with 9.0.10 first. There have been numerous fixes to the permissions code in those 7 releases since 9.0.3. On Fri, Oct 12, 2012 at 2:55 PM, Ashesh Vashi ashesh.va...@enterprisedb.com wrote: Can you please share the log file, found under temp directory? -- Thanks Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Companyhttp://www.enterprisedb.com *http://www.linkedin.com/in/asheshvashi*http://www.linkedin.com/in/asheshvashi On Fri, Oct 12, 2012 at 7:23 PM, devenmtha...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 7601 Logged by: Deven Email address: devenmtha...@gmail.com PostgreSQL version: 9.0.3 Operating system: Windows 2008 R2 WITH SP1 (64 BITS) Description: We are installing our application which internally call postgresql-9.0.3-2-windows_x64.exe to install postgresql under c:\program files folder. But initialization of datbase failed with log that user(administrator) does not have enough permission on data folder. Can anyone help me out to address this issue? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #7601: Installation of PostGresql at c:\Progam files folder does not create right permission on data folder
http://git.postgresql.org/gitweb/?p=edb-installers.git;a=log;h=refs/heads/REL-9_0 On Fri, Oct 12, 2012 at 3:16 PM, Deven Thaker devenmtha...@gmail.comwrote: Hi, Since i am planning to move to 9.0.10. Can someone provide the change log where it is mentioned that this issue is addressed. I went to all feature details of each releases from 9.0.3 to 9.0.10 but i did not find any details which states improvement with respect to fixing an issue with permission problem on folder (data folder). Regards Deven On Fri, Oct 12, 2012 at 7:39 PM, Deven Thaker devenmtha...@gmail.comwrote: Hi Dave,Ashesh Thanks for your prompt response. Since Dave suggested to upgrade version from 9.0.3 to 9.0.10. We will do that. One question is, it was very difficult for us to reproduce an issue even in 9.0.3, after upgrading to 9.0.10 i am not sure whether i will be able to reproduce an issue. But we can always try upgrading version to 9.0.10. Regards Deven On Fri, Oct 12, 2012 at 7:33 PM, Ashesh Vashi ashesh.va...@enterprisedb.com wrote: Hi Deven, As Dave suggested, are you able to reproduce this with the latest version of 9.0.10? -- Thanks Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Companyhttp://www.enterprisedb.com *http://www.linkedin.com/in/asheshvashi*http://www.linkedin.com/in/asheshvashi On Fri, Oct 12, 2012 at 7:30 PM, Deven Thaker devenmtha...@gmail.comwrote: Hi Ashesh, Thanks for your quick response. Unfortunately this happened at customer place and we solved the issue by providing rights to everyone on data folder. We could not take the log from customer. I tried to reproduce couple of times in my environment but could not. But according to my colleague they have faced similar issue many times in our development environment also. Regards Deven On Fri, Oct 12, 2012 at 7:25 PM, Ashesh Vashi ashesh.va...@enterprisedb.com wrote: Can you please share the log file, found under temp directory? -- Thanks Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Companyhttp://www.enterprisedb.com *http://www.linkedin.com/in/asheshvashi*http://www.linkedin.com/in/asheshvashi On Fri, Oct 12, 2012 at 7:23 PM, devenmtha...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 7601 Logged by: Deven Email address: devenmtha...@gmail.com PostgreSQL version: 9.0.3 Operating system: Windows 2008 R2 WITH SP1 (64 BITS) Description: We are installing our application which internally call postgresql-9.0.3-2-windows_x64.exe to install postgresql under c:\program files folder. But initialization of datbase failed with log that user(administrator) does not have enough permission on data folder. Can anyone help me out to address this issue? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] initdb.exe changes --locale option
On Friday, September 14, 2012, Sandeep Thakkar wrote: I think everything is covered by Mike here. getlocales.exe returns the list of locales in the format Language, Country for most of them. and this worked fine on 9.1, but does not work on 9.2. And if we are looking for a workaround in installer, then as Mike suggested, we should handle it in initcluster.vbs. (for 9.2.0) Hmm, thanks Sandeep. So I believe the only thing that changed in this area between 9.1 and 9.2 is that we moved from VC++ 2008 to 2010. Can you confirm that's the only difference please, and that the output from getlocales does differ between versions when run on the same box? If that's the case, we can do the tweaking of the names there, but only when using the newer compiler, if we cannot find a better fix. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] initdb.exe changes --locale option
On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar sandeep.thak...@enterprisedb.com wrote: No.. what I mean to say is that the output from getlocales is same in 9.1 and 9.2. (I checked the installation logs). It's initdb in 9.2 that is not accepting the same output. So, it has nothing to with the VC++ runtimes. Ah, OK. Sorry - misunderstood what you were saying. I guess it could still be the runtimes, but affecting initdb, though a quick look at the initdb commit logs shows this http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a88b6e4cfbff9802906dd400ef334ffa49e7f286, which I'd immediately suspect as at least part of the culprit, except that it was apparently backported to 9.1. PG9.1: -- c:\Program Files\PostgreSQL\9.1bin\initdb.exe --locale=English, New Zealand -D c:\Program Files\PostgreSQL\9.1\data2 The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English, New Zealand. -- OKAY -- PG9.2: -- c:\Program Files\PostgreSQL\9.2bin\initdb.exe --locale=English, New Zealand -D c:\Program Files\PostgreSQL\9.2\data2 The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English_United States.1252--NOT OKAY -- Now, on 9.2, if we replace , with _ from the locale name, then it works fine: c:\Program Files\PostgreSQL\9.2bin\initdb.exe --locale=English_New Zealand -D c:\Program Files\PostgreSQL\data The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English_New Zealand.1252. -- OKAY -- So, actually it's initdb that has undergone change. Fix in initdbcluster.vbs so that the locale name is passed with _ to initdb.exe, is just a workaround from installer. On Fri, Sep 14, 2012 at 3:11 PM, Dave Page dp...@pgadmin.org wrote: On Friday, September 14, 2012, Sandeep Thakkar wrote: I think everything is covered by Mike here. getlocales.exe returns the list of locales in the format Language, Country for most of them. and this worked fine on 9.1, but does not work on 9.2. And if we are looking for a workaround in installer, then as Mike suggested, we should handle it in initcluster.vbs. (for 9.2.0) Hmm, thanks Sandeep. So I believe the only thing that changed in this area between 9.1 and 9.2 is that we moved from VC++ 2008 to 2010. Can you confirm that's the only difference please, and that the output from getlocales does differ between versions when run on the same box? If that's the case, we can do the tweaking of the names there, but only when using the newer compiler, if we cannot find a better fix. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sandeep Thakkar Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91.20.30589514 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] initdb.exe changes --locale option
I note also that two of the special case locales Mike found are ones that are supposed to be handled properly by that patch (they have dots in the name). Here's an earlier attempt, which I believe the second patch was intended to complement: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=d5a7bf8c11c8b66c822bbb1a6c90e1a14425bd6e On Fri, Sep 14, 2012 at 6:54 AM, Dave Page dp...@pgadmin.org wrote: On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar sandeep.thak...@enterprisedb.com wrote: No.. what I mean to say is that the output from getlocales is same in 9.1 and 9.2. (I checked the installation logs). It's initdb in 9.2 that is not accepting the same output. So, it has nothing to with the VC++ runtimes. Ah, OK. Sorry - misunderstood what you were saying. I guess it could still be the runtimes, but affecting initdb, though a quick look at the initdb commit logs shows this http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a88b6e4cfbff9802906dd400ef334ffa49e7f286, which I'd immediately suspect as at least part of the culprit, except that it was apparently backported to 9.1. PG9.1: -- c:\Program Files\PostgreSQL\9.1bin\initdb.exe --locale=English, New Zealand -D c:\Program Files\PostgreSQL\9.1\data2 The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English, New Zealand. -- OKAY -- PG9.2: -- c:\Program Files\PostgreSQL\9.2bin\initdb.exe --locale=English, New Zealand -D c:\Program Files\PostgreSQL\9.2\data2 The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English_United States.1252--NOT OKAY -- Now, on 9.2, if we replace , with _ from the locale name, then it works fine: c:\Program Files\PostgreSQL\9.2bin\initdb.exe --locale=English_New Zealand -D c:\Program Files\PostgreSQL\data The files belonging to this database system will be owned by user edb. This user must also own the server process. The database cluster will be initialized with locale English_New Zealand.1252. -- OKAY -- So, actually it's initdb that has undergone change. Fix in initdbcluster.vbs so that the locale name is passed with _ to initdb.exe, is just a workaround from installer. On Fri, Sep 14, 2012 at 3:11 PM, Dave Page dp...@pgadmin.org wrote: On Friday, September 14, 2012, Sandeep Thakkar wrote: I think everything is covered by Mike here. getlocales.exe returns the list of locales in the format Language, Country for most of them. and this worked fine on 9.1, but does not work on 9.2. And if we are looking for a workaround in installer, then as Mike suggested, we should handle it in initcluster.vbs. (for 9.2.0) Hmm, thanks Sandeep. So I believe the only thing that changed in this area between 9.1 and 9.2 is that we moved from VC++ 2008 to 2010. Can you confirm that's the only difference please, and that the output from getlocales does differ between versions when run on the same box? If that's the case, we can do the tweaking of the names there, but only when using the newer compiler, if we cannot find a better fix. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sandeep Thakkar Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91.20.30589514 Website: www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] initdb.exe changes --locale option
On Fri, Sep 14, 2012 at 10:09 AM, Tom Lane t...@sss.pgh.pa.us wrote: Dave Page dp...@pgadmin.org writes: On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar sandeep.thak...@enterprisedb.com wrote: No.. what I mean to say is that the output from getlocales is same in 9.1 and 9.2. (I checked the installation logs). It's initdb in 9.2 that is not accepting the same output. So, it has nothing to with the VC++ runtimes. Ah, OK. Sorry - misunderstood what you were saying. I guess it could still be the runtimes, but affecting initdb, though a quick look at the initdb commit logs shows this http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a88b6e4cfbff9802906dd400ef334ffa49e7f286, which I'd immediately suspect as at least part of the culprit, except that it was apparently backported to 9.1. Actually, 9.2 intentionally tries to canonicalize locale names, see commit c7cea267de3ca05b29a57b9d113b95ef3793c8d8. Microsoft's support of setlocale seems to be shoddy enough that it wouldn't be surprising if there were some issue there. Oh, OK - thanks for the pointer. I guess this needs further investigation on Windows - I know I'm not likely to be able to look at it for at least a couple of weeks, so if anyone else can... -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] initdb.exe changes --locale option
Sandeep, can you look into this and respond on list please? The thread started here: http://archives.postgresql.org/pgsql-bugs/2012-09/msg00083.php It sounds to me like the OS is at fault for not accepting the name it gives to a locale as input, and that the change to the installer would be a workaround rather than a fix - but I haven't had time to dig into it. Thanks. On Wed, Sep 12, 2012 at 4:53 PM, Mike Toews mwto...@gmail.com wrote: I've found a general solution: with the locale string, replace the first , (comma space) with _. Around line 33 of initcluster.vbs, add: strLocale = Replace(strLocale,, ,_,1,1) I think it is fine to show English, New Zealand in the drop-down menu for the GUI installer, but initcluster.vbs needs to do the replacement to English_New Zealand in order to fulfil the correct initialisation. My testing was conducted using a Python script http://pastebin.com/9epyWz7x which produces a tab delimited table of input locales, and the locale chosen by initdb.exe, as well as the default language for text search configuration. The results from 200 locales shows some significant problems with locale detection, such that most Language, Country are substituted with only one country (you will pick up the pattern if you look at the data). Secondly, there are cases that are completely off: Tamazight (Latin), Algeria : English_United Kingdom.1252, which is corrected to Tamazight (Latin)_Algeria.1252 with the proper substitution. However, there are three corner cases (of 200) that either sort-of breaks things, or doesn't resolve anything: Original: Chinese (Traditional), Macao S.A.R. : Chinese (Traditional)_Taiwan.950 Replaced: Chinese (Traditional)_Macao S.A.R. : English_United Kingdom.1252 Original: Lao, Lao P.D.R. : Lao_Lao P.D.R..1252 Replaced: Lao_Lao P.D.R. : English_United Kingdom.1252 Original: Norwegian (Bokmål), Norway : English_United Kingdom.1252 Replaced: Norwegian (Bokmål)_Norway : English_United Kingdom.1252 (Note: I'm testing on a Windows Vista computer from the UK) Lastly, I had a look at the source code initdb.c, which appears to assume only POSIX locale of the format: [language[_territory][.codeset][@modifier]] E.g., see find_matching_ts_config, which assumes this locale format: http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/bin/initdb/initdb.c;h=824c7fa7e4c76e0a3b8204ce0cdd21564f23d5df;hb=HEAD#l886 It should probably handle the WIN32 logic separately from POSIX locales, but that's a deeper matter. -Mike -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] initdb.exe changes --locale option
Hi On Mon, Sep 10, 2012 at 10:07 PM, Mike Toews mwto...@gmail.com wrote: I'm using the postgresql-9.2.0-1-windows.exe installer, from Enterprise DB, on a Windows Vista 32-bit computer. The issue was noticed with the GUI installer, where I chose the local option English, New Zealand from a drop-down menu, but the resulting database cluster has English_United States.1252. With initdb.exe, I see that --locale has unexpected behaviour. I'll present a few examples that each represent key : value, where key is set with --local=key and value is from the output: The database cluster will be initialized with locale value. C : C English : English_United States.1252 French : French_France.1252 nonsense : English_United Kingdom.1252 French, Canada : French_France.1252 French_Canada : French_Canada.1252 English, Canada : English_United States.1252 English_New_Zealand : English_United Kingdom.1252 English, New Zealand : English_United States.1252 English_New Zealand : English_New Zealand.1252 There are some interesting interpretations in the above, but I understand they probably depend on the OS (Windows Vista, in this Bizzarre. case). In the install-postgresql.log file I see attempts to get a list of available system locales: Executing C:\Users\mwtoews\AppData\Local\Temp\postgresql_installer\getlocales.exe Script exit code: 0 Script output: AfrikaansxxCOMMASPxxSouthxxSPxxAfrica=Afrikaans, South Africa AlbanianxxCOMMASPxxAlbania=Albanian, Albania You can ignore most of that - the weirdness there is just the format we present the data to the Bitrock installer code in for it to populate the list. Ugly as sin, but entirely generated from the local system. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6239: Looking for a technical contact point for PostgreSQL compatibility issue on Windows8
On Saturday, September 1, 2012, Simon Riggs wrote: On 4 October 2011 02:42, Seiko Ishida v-sei...@microsoft.comjavascript:; wrote: The following bug has been logged online: Bug reference: 6239 Logged by: Seiko Ishida Email address: v-sei...@microsoft.com javascript:; PostgreSQL version: 8.2.4 Operating system: Windows 8 Description:Looking for a technical contact point for PostgreSQL compatibility issue on Windows8 Details: Hello, I am a Program Manager with the Ecosystem Engineering team at Microsoft. I am looking for a technical contact point to notify of compatibility issues with PostgreSQL. Could you please connect me to the appropriate individual for this? Regards, Seiko Ishida Microsoft ISV Readiness, EcoSystem Engineering Team Program Manager Ref : 341057 As a general check, I'd like to raise the topic of Window 8 and Windows Server 2012 support. PostgreSQL 9.2 will be released in next few weeks/months, since we are now at release candidate stage. Can I confirm that both Microsoft and PostgreSQL community thinks Windows 8/Server 2012 is fully supported? I can't see build farm members running either of those relases, and there's been no further comments on this issue here. Is somebody doing private testing on behalf of the community? Should we be mentioning Windows8 and Server 2012 support in our release notes? It seems like it could be a feature, or at very least it will be a popular question. OTOH, we don't mention tuned for the Linux 3 kernel, but then perhaps we should be doing that as well... I did some brief testing on one of the Windows 8 preview releases and couldn't find any issues at all. Haven't tried Windows 2012 yet, but wouldn't expect to see any issues there either (Windows is a very stable platform when it comes to backwards compatibility). As far as EDB are concerned, we'll consider the installers to be fully supported on those platforms. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #7482: lack of quotation marks in pg_env script
On Fri, Aug 31, 2012 at 5:17 PM, Bruce Momjian br...@momjian.us wrote: On Tue, Aug 7, 2012 at 12:15:14PM +, m.skrzypkow...@o2.pl wrote: The following bug has been logged on the website: Bug reference: 7482 Logged by: Maciej Skrzypkowski Email address: m.skrzypkow...@o2.pl PostgreSQL version: 9.1.4 Operating system: Windows XP Description: In main application directory, inside pg_env.bat script there is lack of quotation marks for PGDATA and PGLOCALEDIR variables. Dave, has this been addressed? The community does not control pg_env.bat. Not sure - the guy it was assigned to left the company yesterday to pursue an MBA. Sachin, can you check please, and fix if necessary? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7485: 9.2 beta3 libxml2 can't be loaded on Windows
On Wed, Aug 15, 2012 at 2:43 PM, Dave Page dp...@pgadmin.org wrote: On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic rikard.pave...@zg.htnet.hr wrote: On 15.8.2012. 3:54, Craig Ringer wrote: On 08/14/2012 11:42 PM, Rikard Pavelic wrote: On 8.8.2012. 13:30, Craig Ringer wrote: On 08/08/2012 06:24 PM, rikard.pave...@zg.htnet.hr wrote: The following bug has been logged on the website: Bug reference: 7485 Logged by: Rikard Pavelic Email address: rikard.pave...@zg.htnet.hr PostgreSQL version: 9.2 beta3 Operating system: Windows Description: This is still an issue as reported in http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) - The error message you are getting and the command(s) that cause it ERROR: could not set up XML error handler SQL state: 0A000 Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files that PostgreSQL was built with. I'm calling function with type that has an XML attribute. I can provide a test case, but since this is just a warning of the old bug I didn't. OK, I get you. Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? -- Craig Ringer Windows 7 64bit PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit This still seems to be an issue in the test beta4 installers rolled this morning. I'm looking into it. So Sachin and I have looked at this but not found a problem with the installers. He then found that one of our colleagues has already reported this as an issue with PostgreSQL and submitted a possible patch. So, we need a committer to look at fixing this: http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7485: 9.2 beta3 libxml2 can't be loaded on Windows
On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane t...@sss.pgh.pa.us wrote: Dave Page dp...@pgadmin.org writes: So Sachin and I have looked at this but not found a problem with the installers. He then found that one of our colleagues has already reported this as an issue with PostgreSQL and submitted a possible patch. So, we need a committer to look at fixing this: http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php Seems pretty brute-force. Why not just #if LIBXML_VERSION 20703 #define HAVE_XMLSTRUCTUREDERRORCONTEXT #endif in some suitable place (probably xml.c itself, since I don't think we want to #include xmlversion.h in global headers)? Or actually, maybe we could just unconditionally define HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody likely to still be building PG with ancient libxml on Windows? That works for me. Using older libxml's would be a bad idea anyway - and there are precompiled binaries available, so it's not hard to get. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7485: 9.2 beta3 libxml2 can't be loaded on Windows
On Thu, Aug 16, 2012 at 3:28 PM, Dave Page dp...@pgadmin.org wrote: On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane t...@sss.pgh.pa.us wrote: Dave Page dp...@pgadmin.org writes: So Sachin and I have looked at this but not found a problem with the installers. He then found that one of our colleagues has already reported this as an issue with PostgreSQL and submitted a possible patch. So, we need a committer to look at fixing this: http://archives.postgresql.org/pgsql-hackers/2012-06/msg00874.php Seems pretty brute-force. Why not just #if LIBXML_VERSION 20703 #define HAVE_XMLSTRUCTUREDERRORCONTEXT #endif in some suitable place (probably xml.c itself, since I don't think we want to #include xmlversion.h in global headers)? Or actually, maybe we could just unconditionally define HAVE_XMLSTRUCTUREDERRORCONTEXT in pg_config.h.win32. Is anybody likely to still be building PG with ancient libxml on Windows? That works for me. Using older libxml's would be a bad idea anyway - and there are precompiled binaries available, so it's not hard to get. Works as in, I'm happy with it. I haven't tested. Though, it'll likely break some of the old BF animals (temporarily, I hope). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #7485: 9.2 beta3 libxml2 can't be loaded on Windows
On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic rikard.pave...@zg.htnet.hr wrote: On 15.8.2012. 3:54, Craig Ringer wrote: On 08/14/2012 11:42 PM, Rikard Pavelic wrote: On 8.8.2012. 13:30, Craig Ringer wrote: On 08/08/2012 06:24 PM, rikard.pave...@zg.htnet.hr wrote: The following bug has been logged on the website: Bug reference: 7485 Logged by: Rikard Pavelic Email address: rikard.pave...@zg.htnet.hr PostgreSQL version: 9.2 beta3 Operating system: Windows Description: This is still an issue as reported in http://archives.postgresql.org/pgsql-bugs/2012-05/msg00231.php - How you installed PostgeSQL (ie the EnterpriseDB installer, from source, .zip install) I've used EnterpriseDB installer (9.2 beta2 with this bug, and now 9.2 beta3) - The error message you are getting and the command(s) that cause it ERROR: could not set up XML error handler SQL state: 0A000 Hint: This probably indicates that the version of libxml2 being used is not compatible with the libxml2 header files that PostgreSQL was built with. I'm calling function with type that has an XML attribute. I can provide a test case, but since this is just a warning of the old bug I didn't. OK, I get you. Given the context of the old report this sounds like it could be an installation/packaging issue. I'll ping the EDB folks. Which Windows is it exactly? And did you use the 32-bit or 64-bit installer? -- Craig Ringer Windows 7 64bit PostgreSQL 9.2beta3, compiled by Visual C++ build 1600, 64-bit This still seems to be an issue in the test beta4 installers rolled this morning. I'm looking into it. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Mon, Aug 13, 2012 at 7:22 AM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: On 09.08.2012 17:55, Dave Page wrote: On Thu, Aug 9, 2012 at 3:51 PM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: On 09.08.2012 17:07, kargor wrote: I use the binaries provided on the download page. I have not compiled anything - I'm a 'stupid' windows user... Ok, I see. I just downloaded the 9.1.4 installer, and you're right, there is no pldbgapi.control file anywhere. Looking at the README.pldebugger file, the version of pldebugger that the installer includes certainly should include that file. Dave, is this a packaging issue? Which version of pldebugger was included in the 9.1.4 installers? It uses the head of the PRE_9_2 branch. Ok. So, why is pldbgapi.control file not included? It's there in the repository, and make install copies it to share/extension. If it's there in the repo, then it shouldn't be. The PRE_9_2 branch of code is supposed to be how things looked *before* you started your work - it's the stable branch that we're building the 9.2 installers from, and certainly shouldn't have been extensionised, or had any other changes made to it except for bug fixes. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Mon, Aug 13, 2012 at 9:20 AM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: Ok. So, why is pldbgapi.control file not included? It's there in the repository, and make install copies it to share/extension. If it's there in the repo, then it shouldn't be. The PRE_9_2 branch of code is supposed to be how things looked *before* you started your work - it's the stable branch that we're building the 9.2 installers from, and certainly shouldn't have been extensionised, or had any other changes made to it except for bug fixes. Then that was a misunderstanding when we discussed that back in May then (http://archives.postgresql.org/pgadmin-hackers/2012-05/msg00022.php). How do you prefer to resolve that now? The extensionised code in PRE_9_2 branch should work on 9.1, if you include all the right files in the installer, including the control file. Or, we can create a new real pre-9.2 branch at the point before I started any of this work. Or at the point just before the commit that turned it into an extension. All the commits prior to that seem fairly harmless, but would need to test that it works on all supported platforms and server versions. It cannot be extensionised - it's used on 8.x too. I think the best option is to drop the branch, and recreate it from the point immediately prior to your first change, and then cherry pick any important bug fixes you may have made into the new branch. Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Mon, Aug 13, 2012 at 12:54 PM, Magnus Hagander mag...@hagander.net wrote: On Mon, Aug 13, 2012 at 1:51 PM, Craig Ringer ring...@ringerc.id.au wrote: On 08/13/2012 07:19 PM, Heikki Linnakangas wrote: I tried to drop and recreate the branch, but the server would not let me push that change, as it's a non-fast-forward update. Someone needs to temporarily remove the check for that from the git server - I don't think I have access to do that. Do you? pushing with --force didn't work? git push --force origin mybranch Yeah, there is nothing on the git server that should stop you from doing a force push, I believe. There are rules in place to stop it from pushing merge commits, if that has been enabled. But there are no such rules enabled for the pldebugger one. Note of course, which you probably already know, that doing a force push may cause problems for others who have cloned the repository... Yeah - I have a very strong suspicion that's just us though. I've never heard of anyone else working on the debugger (and it's even less likely they'd be working on this branch). Heikki; please try forcing the delete, and let us know if it works OK. I've CC'd Sachin and Ashesh who can drop the old branch from the installer build machines for 8.x and 9.0/9.1. Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Mon, Aug 13, 2012 at 1:57 PM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: On 13.08.2012 15:22, Dave Page wrote: Heikki; please try forcing the delete, and let us know if it works OK. I've CC'd Sachin and Ashesh who can drop the old branch from the installer build machines for 8.x and 9.0/9.1. Ah, I tried forcing the push, didn't help, I got [remote rejected] PRE_9_2 - PRE_9_2 (non-fast-forward) error. However, I succeeded by pushing it in two steps. First, I deleted the branch with git push origin :PRE_9_2, and then pushed it again with git push origin PRE_9_2. So, it's done now. Thanks. Sachin/Ashesh - I guess we probably need to forcibly update the branch on the build servers (or just delete the tree, and let the build script check it out again). Can one of you see to that please? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
On Thu, Aug 9, 2012 at 3:51 PM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: On 09.08.2012 17:07, kargor wrote: I use the binaries provided on the download page. I have not compiled anything - I'm a 'stupid' windows user... Ok, I see. I just downloaded the 9.1.4 installer, and you're right, there is no pldbgapi.control file anywhere. Looking at the README.pldebugger file, the version of pldebugger that the installer includes certainly should include that file. Dave, is this a packaging issue? Which version of pldebugger was included in the 9.1.4 installers? It uses the head of the PRE_9_2 branch. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Re: BUG #6652: Installer grants postgres user rights for the whole disk, not specified subfolder
On Tue, Jul 17, 2012 at 12:01 AM, Trey Chadick tc...@labkey.com wrote: Excerpts from Dave Page's message of mar jun 05 14:38:54 -0400 2012: On Sun, May 20, 2012 at 7:05 PM, Alvaro Herrera alvherre(at)commandprompt(dot)com wrote: I have been installing PostgreSQL 9.1.3.2, and I've noted that 'creating database cluster' is too long. I have been waiting for a half of hour, and it hasn't finished. I've noted that installer calls icacls.exe with arguments: D:\ /grant postgres:RX This seems to be reported every once in a while. It looks like the one-clunk installer is to blame. Maybe it's been fixed in some more recent version -- Dave Page would probably know. Just as an FYI, we are working on this. We've been able to reproduce it, and it appears that icacls (a Microsoft utility) will sometimes look at the ACL of every file/directory recursively when it grants the required privileges on higher level directories. The good news is that in none of the test we've done has it ever modified the ACL on the wrong thing - it just takes a long time if there are a lot of items on the filesystem. We've looked at third party alternatives to icacls, and they seem to exhibit similar traits. We're also going to look into other ways around the root problem. The 9.1.4 installer is still exhibiting this behavior; not as bad as the original bug, but still pushing 30 minutes. Has there been any luck with finding a work-around? Not really, other that removing the check which was specifically added to alleviate issues others saw. However, with 9.2 we're changing the default service account to NT AUTHORITY\NetworkService, which likely doesn't need the check anyway. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6722: Debugger broken?
Hi On Mon, Jul 9, 2012 at 12:58 PM, jan-peter.seif...@gmx.de wrote: The following bug has been logged on the website: Bug reference: 6722 Logged by: Jan-Peter Seifert Email address: jan-peter.seif...@gmx.de PostgreSQL version: 9.1.4 Operating system: Windows 7 Enterprise (64-bit) Description: Hello, it seems that the debugger doesn't work with current minor versions of PostgreSQL. I don't even get the debugging option shown here: http://stackoverflow.com/questions/7865615/debug-postgresql-function-using-pgadmin It could be connected to these changes: http://git.postgresql.org/gitweb/?p=pldebugger.git;a=log I activated the debugger in postgresql.conf and restarted the server(s)): shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' As there only exists the contrib-script I tried to execute this: c:\Program Files\PostgreSQL\9.1\share\contrib\pldbgapi.sql I only get a function not found ( in debugger.dll ) error: FEHLER: konnte Funktion »plpgsql_oid_debug« nicht in Datei »C:/Program Files/PostgreSQL/9.1/lib/plugins/plugin_debugger.dll« finden SQL Status:42883 If I switch to this it works: CREATE OR REPLACE FUNCTION pldbg_oid_debug( OID ) RETURNS INTEGER AS '$libdir/plugins/plugin_debugger' LANGUAGE C STRICT; It's the same with 8.4.12 ( 32-bit ) and 9.0.8 ( 64-bit ). It's the very same install script for each version. In 8.4.12 I also have these two files: c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--1.0.sql and c:\Program Files (x86)\PostgreSQL\8.4\share\contrib\pldbgapi--unpackaged--1.0.sql Obviously they are for PostgreSQL 9.1. The first says install with 'CREATE EXTENSION pldbgapi' There's no such extension - neither in Windows nor Ubuntu ( One click installer and aptitude ) nor in the docs. It looks like it got broken as a result of this commit: http://git.postgresql.org/gitweb/?p=pldebugger.git;a=commit;h=54d993c04809da7cda79013a55b679a615c7dce1 Dharmendra; can you please take a look at this? A quick look at my 9.1 installation shows that the control file is missing along with the SQL scripts. I only have the old pre-extension SQL script from the previous point release (that should really be deleted). For 8.4/9.0 of course, the old installation technique should be used. Please also ensure the docs are appropriate for all branches. Thanks. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6721: installation of PostgreSQL prevented WebServer Start
On Fri, Jul 6, 2012 at 9:29 AM, peter.arn...@jd-ag.com wrote: The following bug has been logged on the website: Bug reference: 6721 Logged by: Peter Arnold Email address: peter.arn...@jd-ag.com PostgreSQL version: 9.0.8 Operating system: MAC OSX Description: Hi, after i install PostgreSQL 9.0.8 on my MAC with OSX 10.7.4 the WEBSERVER is no more able to start. The information about why seems to be: 1. MAC-Webserver is compiled against a libssl.dylib version 0.8.9, PostgreSQL changed this to 1.0.0 2. the libpq.5.dylib is deletet by PostgreSQL and linked to an own lib in the PostgreSQL installation Where did your PostgreSQL distribution come from? The EDB installers certainly won't delete the system libpq, or upgrade the system's copy of libssl.dylib (unless you install it in the root directory of course, which is definitely not recommended!) -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6721: installation of PostgreSQL prevented WebServer Start
On Fri, Jul 6, 2012 at 9:38 AM, Dave Page dp...@pgadmin.org wrote: On Fri, Jul 6, 2012 at 9:29 AM, peter.arn...@jd-ag.com wrote: The following bug has been logged on the website: Bug reference: 6721 Logged by: Peter Arnold Email address: peter.arn...@jd-ag.com PostgreSQL version: 9.0.8 Operating system: MAC OSX Description: Hi, after i install PostgreSQL 9.0.8 on my MAC with OSX 10.7.4 the WEBSERVER is no more able to start. The information about why seems to be: 1. MAC-Webserver is compiled against a libssl.dylib version 0.8.9, PostgreSQL changed this to 1.0.0 2. the libpq.5.dylib is deletet by PostgreSQL and linked to an own lib in the PostgreSQL installation Where did your PostgreSQL distribution come from? The EDB installers certainly won't delete the system libpq, or upgrade the system's copy of libssl.dylib (unless you install it in the root directory of course, which is definitely not recommended!) One of my colleagues has just pointed out that there's some very old (i.e. 2008) code in the installer that creates a symlink from /usr/lib/libpq.5.dylib to the installed copy. This was safe of course (though not the best idea I ever had), prior to Lion. You should be able to put that back how it was by simply replacing the symlink with one pointing to /usr/lib/libpq.5.3.dylib. Apologies for the misinformation. We'll get that bug fixed ASAP. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6721: installation of PostgreSQL prevented WebServer Start
On Fri, Jul 6, 2012 at 11:14 AM, Peter Arnold peter.arn...@jd-ag.com wrote: Hi Dave, my distribution comes from http://www.enterprisedb.com/products-services-training/pgdownload#osx. meanwhile we installed Postgres 8.4.12 and changed the link from /usr/lib/libpq.5.dylib to /usr/lib/libpq.5.3.dylib and both, postgeSQL and Webserver are working. Is it a good Idea to change to PostgreSQL 9.1.x? It's definitely preferable to use 9.1 - though it does have the symlink issue as well. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6705: 32 bit
) 6.12.2.633 Microsoft Visual J# 2.0 Redistributable Package - SE (x64) 2.0.50728 Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 9.0.30729 ActivePerl 5.12.2 Build 1202 5.12.1202 Java Auto Updater 2.0.3.1 Microsoft Visual C++ 2010 x64 Runtime - 10.0.40219 10.0.40219 Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries 6.1.5288.17011 Though the slightly disturbing thing about that is that it isn't listing PostgreSQL, of which I have many versions installed. Not sure why - I'm fairly certain it's not just dumping the windows installer database, as it shows Paint Shop Pro which is a very old product and almost certainly not an MSI based installer. Ick ick ick. I've kept away from this stuff and been happy about it, why do I keep volunteering myself for horrid Windows guts stuff? :-) -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6705: 32 bit
On Wed, Jun 27, 2012 at 7:25 AM, Craig Ringer ring...@ringerc.id.au wrote: On 06/26/2012 06:26 PM, Dave Page wrote: Any ideas for a one-liner to add? I'm struggling to find nice wording, that doesn't invite people to report issues without investigating themselves first: * If you need help, please review http://xx before seeking further assistance. The positive wording is good. Maybe even: Guidance for resolving installation issues can be found at http:// Hmm, yeah, I like that. ... where that provides the common-issues list, a pointer to look at the installation log, then a report template for cases where it wasn't one of the common quick-fixes. I'm happy to work on the docs side, possibly even do a quick JavaScript+form report template to ensure fields like detailed OS version, exact Pg version, etc are supplied. Thanks. We already have some of that on the Wiki, but you know that of course. Which reminds me, I need to find out how to detect whether a Windows box is on a domain with non-default group policy, and how/if antivirus can be detected. Running on a domain is easy (wmic ntdomain), and the AV can either be found in the list of running processes or installed programs I believe. I can't find any way to see if a non-default group policy is (or has previously been) applied. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6705: 32 bit
On Mon, Jun 25, 2012 at 4:38 PM, Craig Ringer ring...@ringerc.id.au wrote: On 06/25/2012 11:10 PM, Dave Page wrote: On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer ring...@ringerc.id.au wrote: Dave: Is there any chance the installers link to that page from their error dialogs, or a static-and-sanitised version of it in docs? If you're ok updating the installer messages I'll collect up a sanitized version that doesn't link to other wiki pages (or make it clear they're external) and convert it for the docs. We can't do clickable links in those message boxes, so I'm not sure how useful it'll be in practice. Argh. I've been in the browser-based app too long, I simply forget that URL handling isn't everywhere. The main ones that IMO need a where-to-go-next hint are the messages that arise when an external process step fails, like initdb, failure to install the runtime, etc. It's always necessary to ask a poster asking for help for the installer log - and how many people don't post or ask for help, just get stuck and confused? Any ideas for a one-liner to add? I'm struggling to find nice wording, that doesn't invite people to report issues without investigating themselves first: * If you need help, please review http://xx before seeking further assistance. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6705: 32 bit
On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer ring...@ringerc.id.au wrote: Dave: Is there any chance the installers link to that page from their error dialogs, or a static-and-sanitised version of it in docs? If you're ok updating the installer messages I'll collect up a sanitized version that doesn't link to other wiki pages (or make it clear they're external) and convert it for the docs. We can't do clickable links in those message boxes, so I'm not sure how useful it'll be in practice. The other question is; on which ones would we want to include extra text? Certainly not all errors/warnings, as some are things like invalid installation directory, which users would just accept, correct their typo or whatever and try again. We wouldn't want to clutter up all message boxes with URLs. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] 9.2 beta2 - pg_ctl crashes on Win32 when neither PGDATA nor -D specified
On Wed, Jun 13, 2012 at 3:51 PM, Bruce Momjian br...@momjian.us wrote: On Mon, Jun 11, 2012 at 10:23:00PM -0400, Tom Lane wrote: Hm, that patch seems to be several bricks shy of a load. I will fix two obvious bugs in it: (1) not dump core on boxes where printf(%s, NULL) dumps core; (2) not try to call adjust_data_dir before complaining for lack of a -D switch; since adjust_data_dir does not do anything to the value of pg_config, it's just silly to do things in that order. However, I note that postgres -C data_directory will refuse to run on the command line because I've got admin privileges in Windows, and that pg_ctl normally starts postgres.exe using CreateRestrictedProcess. But it does not do so for the popen call in adjust_data_dir. if that actually is a third bug, as seems likely, somebody with access to a windows environment will need to deal with it. I think you have to use RUNAS when using 'pg_ctl' or 'postgres' on Windows. pg_ctl should work as an administrative user, as it'll irrevocably drop unwanted privileges. postgres won't though. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] 9.2 beta1 libxml2 can't be loaded on Windows
Sachin, please investigate ASAP. Thanks. On Mon, Jun 11, 2012 at 6:30 AM, Edmund Horner ejr...@gmail.com wrote: On 9 June 2012 03:48, Dave Page dp...@pgadmin.org wrote: On Fri, Jun 1, 2012 at 1:39 AM, Edmund Horner ejr...@gmail.com wrote: On 1 June 2012 12:36, Edmund Horner ejr...@gmail.com wrote: On 1 June 2012 12:14, Edmund Horner ejr...@gmail.com wrote: I tried using an older libxml2.dll. Replace with the one from ftp://ftp.zlatkovic.com/libxml/oldreleases/libxml2-2.6.9.win32.zip (and copying zlib1.dll to zlib.dll), and it works. ... Please test 9.2 beta 2 - that's the first build to come from the new build machine that'll be used for this release. It's got a new set of dependencies which should all work correctly. Hi Dave, I've tried with the EnterpriseDB.com Windows 32-bit 9.2 beta2 installer found via his page: http://www.postgresql.org/download/snapshots/ Previously I was testing with the plain binaries zip, but those don't seem to be available for beta2 yet. The problem still occurs. Again, I can work past it by copying in an old version of libxml2.dll and zlib.dll. Edmund. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6688: can't install from binary.
On Mon, Jun 11, 2012 at 6:12 PM, om...@ra1.net wrote: The following bug has been logged on the website: Bug reference: 6688 Logged by: Rob Email address: om...@ra1.net PostgreSQL version: 9.1.4 Operating system: OSX 10.4.11 Description: Hi, I get an error when trying to run the 9.1.4 installer binary (postgresql-9.1.4-1-osx.app) on my Mac PowerBook PPC running OS X 10.4.11. It says, Bad CPU type in executable. Your download page says that OS X 10.4 on PPC is supported -- A one click installer is available for for Mac OS X 10.4 and above on Intel and PPC and includes PostgreSQL, pgAdmin, PL/Java and the PL/pgSQL debugger plugin.' http://www.postgresql.org/download/macosx/ What am I missing? Or what might I be doing wrong? I simply downloaded the disk image and tried to run the installer. Only the 8.3 and 8.4 installers still support PPC I'm afraid. We'll need to clarify that text. Sorry for the inconvenience. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] 9.2 beta1 libxml2 can't be loaded on Windows
On Fri, Jun 1, 2012 at 1:39 AM, Edmund Horner ejr...@gmail.com wrote:
On 1 June 2012 12:36, Edmund Horner ejr...@gmail.com wrote:
On 1 June 2012 12:14, Edmund Horner ejr...@gmail.com wrote:
I tried using an older libxml2.dll. Replace with the one from
ftp://ftp.zlatkovic.com/libxml/oldreleases/libxml2-2.6.9.win32.zip
(and copying zlib1.dll to zlib.dll), and it works.
I note that the previous 9.1.3 binaries used the newer libxml2.dll
though (same as the one in
ftp://ftp.zlatkovic.com/libxml/libxml2-2.7.8.win32.zip).
So I'm guessing the Windows PostgreSQL binaries were built with the
old one, but packaged with the new one.
Also, if libxml2.dll is replaced with the 2.6 version as above,
CREATE EXTENSION xml2 will result in this:
ERROR: could not load library C:/ehorner/pgsql/lib/pgxml.dll:
The specified procedure could not be found.
Which may imply that that DLL was built with the 2.7 version. With
the 2.7 version in place as originally packaged, we have can load the
extension but not use the functions from it.
postgres=# create extension xml2;
CREATE EXTENSION
postgres=# select xslt_process('foo/', 'bar/');
ERROR: could not set up XML error handler
HINT: This probably indicates that the version of libxml2 being
used is not compatible with the
libxml2 header files that PostgreSQL was built with.
I wanted to check whether the packaged libxslt.dll had the same
compatibility situation as libxml2.dll does. Unfortunately it seems
doing so means using both versions of the library at once!
Edmund.
Argh, I forget to mention the packaged pgadmin3.exe (in the same bin
dir as postgres) wants the 2.7 version of the DLL (as packaged).
Hi
Please test 9.2 beta 2 - that's the first build to come from the new
build machine that'll be used for this release. It's got a new set of
dependencies which should all work correctly.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6652: Installer grants postgres user rights for the whole disk, not specified subfolder
On Wed, Jun 6, 2012 at 8:04 PM, Basil Peace gr...@yandex.ru wrote: In my case invalid argument (root directory instead of specified data directory) was passed by installer to icacls. That's what I saw. It wasn't problem of icacls, it was a problem in pgsql installer. That's supposed to happen. It sets the permissions on the data directory and then recurses back up to the root directory, ensuring the postgres account is able to read all the parent directories - otherwise, even if it has write permissions on the data directory itself, it cannot access it. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6652: Installer grants postgres user rights for the whole disk, not specified subfolder
On Sun, May 20, 2012 at 7:05 PM, Alvaro Herrera alvhe...@commandprompt.com wrote: Excerpts from grv87's message of sáb may 19 10:28:47 -0400 2012: The following bug has been logged on the website: Bug reference: 6652 Logged by: Basil Peace Email address: gr...@yandex.ru PostgreSQL version: 9.1.3 Operating system: Windows 7 x64 Description: I have been installing PostgreSQL 9.1.3.2, and I've noted that 'creating database cluster' is too long. I have been waiting for a half of hour, and it hasn't finished. I've noted that installer calls icacls.exe with arguments: D:\ /grant postgres:RX This seems to be reported every once in a while. It looks like the one-clunk installer is to blame. Maybe it's been fixed in some more recent version -- Dave Page would probably know. Just as an FYI, we are working on this. We've been able to reproduce it, and it appears that icacls (a Microsoft utility) will sometimes look at the ACL of every file/directory recursively when it grants the required privileges on higher level directories. The good news is that in none of the test we've done has it ever modified the ACL on the wrong thing - it just takes a long time if there are a lot of items on the filesystem. We've looked at third party alternatives to icacls, and they seem to exhibit similar traits. We're also going to look into other ways around the root problem. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6652: Installer grants postgres user rights for the whole disk, not specified subfolder
On Tue, Jun 5, 2012 at 7:48 PM, Alvaro Herrera alvhe...@commandprompt.com wrote: Excerpts from Dave Page's message of mar jun 05 14:38:54 -0400 2012: On Sun, May 20, 2012 at 7:05 PM, Alvaro Herrera alvhe...@commandprompt.com wrote: I have been installing PostgreSQL 9.1.3.2, and I've noted that 'creating database cluster' is too long. I have been waiting for a half of hour, and it hasn't finished. I've noted that installer calls icacls.exe with arguments: D:\ /grant postgres:RX This seems to be reported every once in a while. It looks like the one-clunk installer is to blame. Maybe it's been fixed in some more recent version -- Dave Page would probably know. Just as an FYI, we are working on this. We've been able to reproduce it, and it appears that icacls (a Microsoft utility) will sometimes look at the ACL of every file/directory recursively when it grants the required privileges on higher level directories. The good news is that in none of the test we've done has it ever modified the ACL on the wrong thing - it just takes a long time if there are a lot of items on the filesystem. We've looked at third party alternatives to icacls, and they seem to exhibit similar traits. We're also going to look into other ways around the root problem. Maybe you should provide some way for the user to figure out the exact command it's running, where it's running it, and what user it runs as. Not sure why/how that would help. We know what we've told it to do, and why - we just don't know why the Microsoft utility insists on looking at the ACLs of files it should have no need to touch. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6647: Password Issue
On Tue, May 29, 2012 at 5:00 AM, Craig Ringer ring...@ringerc.id.au wrote: On 05/23/2012 04:00 AM, Robert Haas wrote: On Thu, May 17, 2012 at 5:43 AM,subu@gmail.com wrote: The following bug has been logged on the website: Bug reference: 6647 Logged by: Subramanian Email address: subu@gmail.com PostgreSQL version: 9.1.3 Operating system: Windows XP Description: Hello there. We in our company using your product of PostgreSQL - 9.1.3 8.3. But both of these products results in a Password Error. We all tried with variuos passwords and got a Single error as Failed... Please respond to this bug ASAP. Thank you. You probably have an existing postgres account. Try changing the password of that account to something that you know, and then using that password for the installer. I really wish EDB would add a help link to this part of the installer, it bits people all the time. It's on my TODO - added a couple of weeks ago. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6591: pg_dump version not compatible
On Sun, Apr 15, 2012 at 7:07 PM, helgistei...@gmail.com wrote: The following bug has been logged on the website: Bug reference: 6591 Logged by: Helgi Steinar Email address: helgistei...@gmail.com PostgreSQL version: 9.1.3 Operating system: Mac OSX 10.7.3 Description: I downloaded and installed the version of Postgres using the installer from http://www.enterprisedb.com/products-services-training/pgdownload#osx When trying to use pg_dump the result is pg_dump: server version: 9.1.3; pg_dump version: 9.0.5 Use the pg_dump executable that came with the installer (normally installed in /Library/PostgreSQL/9.1/bin) - you're almost certainly using the older, Apple supplied one in /usr/bin. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Bug in postgresql 8.1
On Sunday, March 18, 2012, Jaime Casanova ja...@2ndquadrant.com wrote: On Sun, Mar 18, 2012 at 12:13 AM, prem tolani premtol...@yahoo.com wrote: Below error occurs only when i restart postgre 8.1 service when applicaion is running. Otherwise it works fine, but while application is running and i restart postgre 8.1 service. Application crashes. Please refer to below email. postgres 8.1 is not currently supported (since November 2010, http://www.postgresql.org/support/versioning), so is likely that if something was done in postgres to support win7 it hasn't reach 8.1 It hasn't been supported on Windows for *much* longer. the best fix you can get is to migrate to a newer supported version as soon as possible. +1. Windows 7 will never be a supported platform for 8.1, even if it was still supported in general. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on initialising the database cluster (with work-around)
On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal dharmendra.go...@enterprisedb.com wrote: On Sat, Jan 28, 2012 at 2:17 AM, Eric Borts ebo...@bltek.com wrote: The installation now runs successfully after deleting that registry key. In addition, I tried changing the default action on batch files from Open to Edit using the registry (Windows 7). Double-clicking a file opens it in Notepad, but the installation runs successfully. So it looks like the UserChoice registry key, however it got there, is the essence of the problem. Which, of course, %COMSPEC% /c would avoid because the program handling batch files is explicit. Nice analysis Eric. ANy idea why (which program set this) this particular registry was set. Dave, shall we consider using %COMSPEC% /c with 0 as second parameter..?? We can certainly try it, though I'm concerned it may break more systems than it fixes, eg. those where %COMSPEC% has been intentionally changed because the use wants to use a different shell. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on initialising the database cluster (with work-around)
On Mon, Jan 30, 2012 at 7:49 AM, Eric Borts ebo...@bltek.com wrote: On 1/29/2012 3:02 AM, Dave Page wrote: On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal dharmendra.go...@enterprisedb.com wrote: Nice analysis Eric. ANy idea why (which program set this) this particular registry was set. Dave, shall we consider using %COMSPEC% /c with 0 as second parameter..?? We can certainly try it, though I'm concerned it may break more systems than it fixes, eg. those where %COMSPEC% has been intentionally changed because the use wants to use a different shell. I'd have to agree with Dave here. It was clearly a problem with my batch file association. I don't know *how* I got into this state, but at least there's a good log now of how to fix the problem for users that have the same problem! I suppose you could detect the problem and issue warning by running a test echo batch file and *not waiting* on the result, then pausing for a second, and checking to see if the output file was created. Heck or check the registry to see if there's a UserChoice key on the .bat extension. In any case, I'm satisfied that my computer was messed up and it's now fixed. And I've got my context menu back! That's the most important thing! Thanks for the hard work and excellent analysis of the problem. Regards, Dave. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs on initialising the database cluster (with work-around)
iirc, using %COMSPEC% /c will cause the scripts to run in a visible command window, which is pretty ugly, and doesn't seem to be necessary anywhere except on your machine! What's the output from the set command on that box? On Thu, Jan 26, 2012 at 6:54 PM, Eric Borts ebo...@bltek.com wrote: Also, here is a link to the same issue on StackOverflow: http://stackoverflow.com/questions/3559719/wscript-shell-run-doesnt-work-consistently Also solved using %COMSPEC% /c, though it doesn't say why this is a problem. Cheers, Eric On 1/26/2012 11:37 AM, Eric Borts wrote: On 1/26/2012 1:17 AM, Dave Page wrote: Dharmendra, can you look into this please? Eric, is there anything unusual about the configuration of your machine? Suffice it to say, this doesn't normally happen. Hi Dave, I'm guessing the answer to that question is yes. The machine came preinstalled with Norton Internet Security, but this was turned off when I ran the install. After further investigation to the .bat file, I realized that I am also missing the Edit option when I right click a batch file. I investigated, uninstalled stuff, disabled a lot of stuff in my registry, and nearly bricked my computer. After three hours, I'm going to have to ask for suggestions. Here's what I found/tried: 1. uninstalled Norton Internet Security (and rebooted) 2. uninstalled Acrobat Reader 3. disabled all ContextMenuHandlers by a. renaming HKCR/*/shellex to oldshellex b. renaming HKCR/AllFileSystemsObjects/shellex to oldshellex c. tried, but was unable to rename HKCR/batfile/ShellEx, so renamed HKCR/batfile/ShellEx/ContextMenuHandlers to oldContextMenuHandlers 4. disabled all non-Microsoft shell extensions using ShellExView 5. rebooted - computer bricked (black screen when Windows should be loading) 6. booted in safe mode 7. tested script (from my original response) and right click. a. no Edit option in batch file context menu b. script hung as before 8. Undid steps 3 and 4 in safe mode 9. Rebooted - booted into windows properly 10. Still no Edit in context menu and script still hangs I'm open to suggestions. I think it might be related to Edit menu missing from my batch file, as this is the only odd thing that I can tell about my machine. I have another similar machine (earlier model Vaio) that both has the Edit menu and runs the test script successfully. I compared the HKCR/batfile registry trees (using TortoiseSVN diff) and they are identical. Short of comparing the entire registry I'm at a loss. Would it be too dangerous to use WScript.Shell.Exec or to use WScript.Shell.Run %COMPSEC% /c ? This has been an 11 hour struggle for me so far, and I know at least a few others have had this same problem. Here is a link to my work around on enterprisedb. Thanks, Eric Reference Links: http://www.pcreview.co.uk/forums/edit-print-open-missing-shell-context-menu-cmd-and-bat-files-t2551124.html http://windowsxp.mvps.org/slowrightclick.htm http://www.nirsoft.net/utils/shexview.html -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Wednesday, October 5, 2011, Thomas Kellerer spam_ea...@gmx.net wrote: Dave Page, 04.10.2011 21:46: We updated our build system to use BitRock 7 today (for unrelated reasons) which has new features for ACL management. We're going to investigate replacing cacls/icacls with those features tomorrow and will create some test builds ASAP. If you can provide the test builds publicly, I will be happy to test them and see if that behaves differently on my system. Thanks, we will. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Mon, Oct 3, 2011 at 2:15 PM, Dave Page dp...@pgadmin.org wrote: On Mon, Oct 3, 2011 at 9:42 AM, Thomas Kellerer spam_ea...@gmx.net wrote: Dave Page wrote on 03.10.2011 10:11: Karl; can you please provide precise details of your Windows version, and anything unusual about your disk configuration? I know this doesn't happen on any of the installations of Windows 7 that we use for testing (which tend to be the MSDN builds, running on local NTFS disks), so I wonder if there's an icacls bug in a specific build or rev of Windows, or when used on a certain type of filesystem. I have reported this as well some weeks ago. For me this happened on a Windows7 64 bit system that is part of a domain (all current MS patches applied) UAC is turned off, I was logged in as a local administrator (*not* a domain administrator). I have a ProcessMonitor trace that shows the behaviour of what icacls is doing when started by the installer. It is available here: http://www.sql-workbench.net/icacls_trace.zip Thanks Thomas. That certainly doesn't look like it's doing what it was told to :-s We've been looking at this today, and whilst we haven't found icacls changing any ACLs that it shouldn't, we have no seen it reading the ACLs of files on the entire disk. I've also found a couple of similar reports on the net. We updated our build system to use BitRock 7 today (for unrelated reasons) which has new features for ACL management. We're going to investigate replacing cacls/icacls with those features tomorrow and will create some test builds ASAP. Oh, the joys of supporting Windows :-) -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6237: Hang during install database initialization
On Tue, Oct 4, 2011 at 6:02 PM, jim.g...@bull.com wrote: Can I get you to check the task manager for icacls while the install is hung? Yes, I did notice icacls.exe running when I used the task manager to see what processes were consuming cpu cycles or doing disk writes. In fact, icacls.exe was the only thing using the cpu or the disk; the postgres process was idle. I also noticed this icacls.exe issue being discussed in the bug mailing list after I had already submitted my bug report. I've just sent an update to that thread, and will direct any future updates there for the sake of everyone's sanity. http://archives.postgresql.org/pgsql-bugs/2011-10/msg4.php -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Wednesday, October 5, 2011, Craig Ringer ring...@ringerc.id.au wrote: On 10/05/2011 03:46 AM, Dave Page wrote: Oh, the joys of supporting Windows :-) It's funny: for an OS with so relatively few flavours and versions, the number of quirks and bizarre behaviors is quite remarkable. I guess the text matrix isn't small, though: Windows XP / Vista / 7 / [8] You forgot 2003, 2003R2, 2008 and 2008R2 32-bit / 64-bit Basic / Home / Pro or Business / Enterprise / Ultimate / Embedded Standard, Enterprise and Datacenter for the server editions. On a domain / standalone Local admin account / non-admin account / UAC admin account Domain admin. [too many different antivirus products to list] Service packs *endless* possible group policy configurations ... so it's not too surprising to see hard-to-reproduce weirdness popping up. That last one is one of the worst - I've seen all sorts of weird policies from government users and large companies - they can take a *lot* of figuring out. That's why we have 4 developers who work on the installers (not all the time of course, but often in busy bursts for a few days or more, and often in parallel, like today with 3 guys working on this issue), along with 2 QA guys when we're building releases. It's easy to think building and maintaining installers is easy - unfortunately, that can be very far from the case for a product like Postgres. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Mon, Oct 3, 2011 at 8:59 AM, Magnus Hagander mag...@hagander.net wrote: On Fri, Sep 30, 2011 at 15:34, Karl Wright daddy...@gmail.com wrote: I saw a thread where somebody saw icacls.exe being called by the one-click installer. I'm having the same thing - the installer has been running for 45 minutes now and is basically going to have to be stopped because I'm out of time waiting for it. Looking at process monitor, it is clear that icacls.exe is going through every file on the entire system and changing its permissions. The process tree indicates that it is a child of the installer, and that it is running the command: icacls C:\ /grant kawright:RX Clearly this won't do at all and should be considered a severe installer bug. If it does, it certainly sounds like a very bad bug. However, according to the documentation for icacls (http://technet.microsoft.com/en-us/library/cc753525(WS.10).aspx), you should use /t to get it to traverse into subdirectories, and clearly it's not doing that. So I wonder why it would go across the whole filesystem - might tbere be a bug in icacls? Yes - that's how it's supposed to work (ie. *not* using /t). The purpose of that code is to ensure that the entire path leading up to the data/installation directories is readable by the users that need it. We've had a number of reported installation failures in the past caused by weirdness where read or execute permissions weren't available for (for example) the service account user, which caused somewhat mysterious failures. Or maybe it has something to do with inheritance? The way inheritance-permissions works on ntfs is, um, let's call it interesting. Maybe it needs to specify the (NP) flag to not propagate inheritance or something? Sachin/Ashesh; can one of you investigate this please? Karl; can you please provide precise details of your Windows version, and anything unusual about your disk configuration? I know this doesn't happen on any of the installations of Windows 7 that we use for testing (which tend to be the MSDN builds, running on local NTFS disks), so I wonder if there's an icacls bug in a specific build or rev of Windows, or when used on a certain type of filesystem. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
Thanks Karl. Is SP1 installed? Sachin, Ashesh - anything else you can think of that would be useful? On Mon, Oct 3, 2011 at 1:48 PM, Karl Wright daddy...@gmail.com wrote: Sorry for the delay - it's been a busy morning. The Windows 7 system I'm using is a laptop with a standard basic Nokia image. To the best of my knowledge there have been no OEM modifications of any kind. It describes itself as Windows 7 Enterprise, and says it is 32-bit. That's it. Anything else you'd want me to check? Karl On Mon, Oct 3, 2011 at 4:11 AM, Dave Page dp...@pgadmin.org wrote: On Mon, Oct 3, 2011 at 8:59 AM, Magnus Hagander mag...@hagander.net wrote: On Fri, Sep 30, 2011 at 15:34, Karl Wright daddy...@gmail.com wrote: I saw a thread where somebody saw icacls.exe being called by the one-click installer. I'm having the same thing - the installer has been running for 45 minutes now and is basically going to have to be stopped because I'm out of time waiting for it. Looking at process monitor, it is clear that icacls.exe is going through every file on the entire system and changing its permissions. The process tree indicates that it is a child of the installer, and that it is running the command: icacls C:\ /grant kawright:RX Clearly this won't do at all and should be considered a severe installer bug. If it does, it certainly sounds like a very bad bug. However, according to the documentation for icacls (http://technet.microsoft.com/en-us/library/cc753525(WS.10).aspx), you should use /t to get it to traverse into subdirectories, and clearly it's not doing that. So I wonder why it would go across the whole filesystem - might tbere be a bug in icacls? Yes - that's how it's supposed to work (ie. *not* using /t). The purpose of that code is to ensure that the entire path leading up to the data/installation directories is readable by the users that need it. We've had a number of reported installation failures in the past caused by weirdness where read or execute permissions weren't available for (for example) the service account user, which caused somewhat mysterious failures. Or maybe it has something to do with inheritance? The way inheritance-permissions works on ntfs is, um, let's call it interesting. Maybe it needs to specify the (NP) flag to not propagate inheritance or something? Sachin/Ashesh; can one of you investigate this please? Karl; can you please provide precise details of your Windows version, and anything unusual about your disk configuration? I know this doesn't happen on any of the installations of Windows 7 that we use for testing (which tend to be the MSDN builds, running on local NTFS disks), so I wonder if there's an icacls bug in a specific build or rev of Windows, or when used on a certain type of filesystem. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Mon, Oct 3, 2011 at 9:42 AM, Thomas Kellerer spam_ea...@gmx.net wrote: Dave Page wrote on 03.10.2011 10:11: Karl; can you please provide precise details of your Windows version, and anything unusual about your disk configuration? I know this doesn't happen on any of the installations of Windows 7 that we use for testing (which tend to be the MSDN builds, running on local NTFS disks), so I wonder if there's an icacls bug in a specific build or rev of Windows, or when used on a certain type of filesystem. I have reported this as well some weeks ago. For me this happened on a Windows7 64 bit system that is part of a domain (all current MS patches applied) UAC is turned off, I was logged in as a local administrator (*not* a domain administrator). I have a ProcessMonitor trace that shows the behaviour of what icacls is doing when started by the installer. It is available here: http://www.sql-workbench.net/icacls_trace.zip Thanks Thomas. That certainly doesn't look like it's doing what it was told to :-s -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] [GENERAL] One-click installer, Windows 7 32-bit, and icacls.exe
On Mon, Oct 3, 2011 at 2:39 PM, mgo...@isstrucksoftware.net wrote: I am running Windows 7 x64 (version 6.1.7601). My copy is also from the MSDN with latest updates applied. When I get to the end of the postgres install I get a error: Problem running post-install step. Installation may not complete correctly. The database cluster initialisation failed. I very much doubt that s the issue being discussed here. I'd suggest starting a new thread on pgsql-bugs and including your installation logs from %TEMP%. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company top.letterhead
Re: [BUGS] BUG #6223: Installation with service account
On Mon, Sep 26, 2011 at 9:40 AM, Ola van Dunen vandu...@smart-interfaces.de wrote: The following bug has been logged online: Bug reference: 6223 Logged by: Ola van Dunen Email address: vandu...@smart-interfaces.de PostgreSQL version: 9.* Operating system: Windows Server 2008 Description: Installation with service account Details: In order to run this database as a service under Windows Server 2008 R2 one is forced to install the active directory and to install the database at the same location of the to be installed domain controller which is basically an architectural bug to me. Whose packages are you using? That's certainly not the case with the EnterpriseDB installers. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6224: Installation Error of dotconnect for postgre SQL Professional
On Mon, Sep 26, 2011 at 3:02 PM, Dean Heller dhel...@tainstruments.com wrote: The following bug has been logged online: Bug reference: 6224 Logged by: Dean Heller Email address: dhel...@tainstruments.com PostgreSQL version: 4.95.170.0 Operating system: Windows 7 64bit Description: Installation Error of dotconnect for postgre SQL Professional Details: The following error is generated when installing the componet dotconnect for postgre SQL Professional on Windows 7 64bit OS --- Custom action error: CrGacUtil Date: 9/26/2011 6:34:19 AM Environment Operating System: Microsoft Windows NT 6.1.7600.0 .NET Framework: 2.0.50727.4927 Assembly: CrGacUtil, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701 Exception Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Type: Devart.Common.Setup.CustomActionException StackTrace: at CrGacUtil.Program.Main(String[] args) CustomMessage: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Inner Exception Message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Type: Devart.Common.Setup.CustomActionException StackTrace: at CrGacUtil.Program.Main(String[] args) dotConnect isn't a project run by the PostgreSQL community, but a commercial product from Devart. You should report this issue to them. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6194: Cannot install any of the installers
On Friday, September 2, 2011, Pradeep D pradeep.dharmavar...@live.com wrote: The following bug has been logged online: Bug reference: 6194 Logged by: Pradeep D Email address: pradeep.dharmavar...@live.com PostgreSQL version: all Operating system: Windows 7 64 bit SP1 Description:Cannot install any of the installers Details: I keep getting these errors - 1. Unable to write inside TEMP environment variable path 2. An error occured executing the Microsoft VC++ runtime installer The first message is with 9.x installer version and the second is with 8.x versions. I am the admin on my machine. I also have Windows Scripting active and also disable my antivirus and firewall while installing these packages. Please help with any instructions to fix this issue. The older installers are probably giving the second error as they didn't have the same check as the first to ensure that the environment was sane before trying to install the runtimes. What it's saying is that it cannot write a file and execute it from your temporary directory. What does %TEMP% point to, and does that directory exist? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #6191: One click installer fails
On Thu, Sep 1, 2011 at 2:47 AM, Mark Lamberton m...@penguinsystems.com.au wrote: The following bug has been logged online: Bug reference: 6191 Logged by: Mark Lamberton Email address: m...@penguinsystems.com.au PostgreSQL version: 9.0.4-1 Operating system: Windows 7 Description: One click installer fails Details: Problem signature: Problem Event Name: BEX Application Name: install.exe_Microsoft® Visual Studio® 2008 Application Version: 9.0.30729.4148 Unfortunately that's the Microsoft VC++ 2008 runtime installer thats failing, not ours (we just embed theirs). If you already have them installed (which is quite often the case), or install them manually using the installer Microsoft offer on their download site - which is a different one from the one we're allowed to embed - you could then try running our installer from the command line using the option: --install_runtimes 0 -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] libber library not found on RC1
On Thu, Aug 25, 2011 at 3:17 PM, Tom Lane t...@sss.pgh.pa.us wrote: alexondi alexo...@rambler.ru writes: I update server to RC1 version and after call pg_ctl to start I get this error opt/PostgreSQL/9.1/bin/pg_ctl: error while loading shared libraries: liblber-2.3.so.0: cannot open shared object file: No such file or directory But I have 2.4 version of this library. And I see in ldd pg_ctl that this library was added in RC or why I can't start server without ldap auth? How did you install RC1? The only obvious explanation for this error is that you are trying to use somebody else's executables that were built for a different environment than you have (specifically, wanting different revision numbers of some shared libraries). If so, you may need to build the software locally to get something that will work for you. It's an installer bug that's being worked on at the moment (we added LDAP support, and ran into an rpath issue). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6169: a non fatal error occured during cluster.... problem with environment variables
On Fri, Aug 19, 2011 at 2:19 PM, ondro balu...@horizon.sk wrote: The following bug has been logged online: Bug reference: 6169 Logged by: ondro Email address: balu...@horizon.sk PostgreSQL version: 8.4.8 Operating system: WindowsXP Description: a non fatal error occured during cluster problem with environment variables Details: During instalation error occur a non fatal error occured during cluster initialisation and after instalation postgresql not work. Problem is that postgresql instalation expect in the windows environment variables path c:\windows\system32. If not set path c:\windows\system32 or doesn`t work instalation fail with this error. Why on earth would the system32 directory not be in the path? That's the *nix equivalent of not having /bin and /sbin in the path. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6164: Flashing dialog
On Tue, Aug 16, 2011 at 8:11 PM, Josh Kupershmidt schmi...@gmail.com wrote: On Mon, Aug 15, 2011 at 11:31 PM, Kyle Fox kyle@gmail.com wrote: I used the installer to install Postgres 9.0 on my Mac, and now every 10 seconds a dialog message flashes and immediately disappears, and STEALS FOCUS. The focus-stealing sounds like a problem coming from the EDB installer you said you used, and you'll have to complain to those folks about it. No it doesn't, unless the OP has found some weird bug in pgAdmin or StackBuilder. Sounds to me more like OSX is throwing the dialogue for some reason when the launch daemon tries to load the service. Try running: sudo launchctl unload /Library/LaunchDaemons/com.edb.launchd.postgresql-8.4 That should stop it trying to start the server, at least until the next reboot (enough to hopefully see if the focus issue is resolved). To completely uninstall, use sudo open /Library/PostgreSQL/8.4/uninstall-postgresql.app/ -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6164: Flashing dialog
On Tue, Aug 16, 2011 at 8:24 PM, Dave Page dp...@pgadmin.org wrote: On Tue, Aug 16, 2011 at 8:11 PM, Josh Kupershmidt schmi...@gmail.com wrote: On Mon, Aug 15, 2011 at 11:31 PM, Kyle Fox kyle@gmail.com wrote: I used the installer to install Postgres 9.0 on my Mac, and now every 10 seconds a dialog message flashes and immediately disappears, and STEALS FOCUS. The focus-stealing sounds like a problem coming from the EDB installer you said you used, and you'll have to complain to those folks about it. No it doesn't, unless the OP has found some weird bug in pgAdmin or StackBuilder. For the benefit of the list archives, the OP just told me that the dialog responsible for steal focus was coming from his firewall. He's fixed that, and completed a fresh installation. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6120: Problem running post-install step in Mac OS X Lion (GM)
On Mon, Jul 18, 2011 at 8:40 PM, Paula Andrea Carvajal Díaz paanc...@gmail.com wrote: I am testing Mac OS X Lion (Gold Master). Log file attached. Thanks. I think it's pretty safe to say I'm not going to be able to do much with this until I get my hands on a copy of Lion I'm afraid. The log shows some unexpected output, particularly: Executing /Library/PostgreSQL/9.0/installer/server/createuser.sh postgres /Library/PostgreSQL/9.0 Script exit code: 0 Script output: User account 'postgres' already exists Script stderr: su: unknown login: postgres - -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6122: Installation fails: database cluster initialisation failed
On Tue, Jul 19, 2011 at 9:38 AM, Mike Holywell m...@segment8.co.uk wrote: The following bug has been logged online: Bug reference: 6122 Logged by: Mike Holywell Email address: m...@segment8.co.uk PostgreSQL version: 9.0.4 Operating system: Mac OSX 10.7 (Lion) Description: Installation fails: database cluster initialisation failed Details: On a fresh install of Lion (11A511) installing Postgres 9.0.4 fails Problem running post-install step installation may not complete correctly The database cluster initialisation failed This has been reported on other blogs eg http://seeboriscode.blogspot.com/2011/06/osx-107-lion-postgres-installation. html I've had a similar(?) problem with the dscl command not creating the user under earlier Lion Betas The installers don't yet support Lion. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6120: Problem running post-install step in Mac OS X Lion (GM)
On Sun, Jul 17, 2011 at 2:01 AM, Paula Andrea Carvajal paanc...@gmail.com wrote: The following bug has been logged online: Bug reference: 6120 Logged by: Paula Andrea Carvajal Email address: paanc...@gmail.com PostgreSQL version: 9.0.4 Operating system: Mac OS X 10.7 (GM) Description: Problem running post-install step in Mac OS X Lion (GM) Details: Problem using EnterpriseDB Mac OS X Installer version Version 9.0.4-1 (from http://www.enterprisedb.com/products-services-training/pgdownload). OS X Lion is not yet supported (it's not even released yet). If you send the installation log, we can probably figure out what went wrong though. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] application_name appears in Reporting and logging
On Tuesday, July 12, 2011, Emanuel Calvo postgres@gmail.com wrote: I don't know but seems to be incorrect, it is really in this category? Version 9.1 beta 2 postgres=# select * from pg_settings where name = 'application_name'; -[ RECORD 1 ] name | application_name setting | psql unit | category | Reporting and Logging / What to Log short_desc | Sets the application name to be reported in statistics and logs. extra_desc | context | user vartype | string source | client That is per design - why does it seem wrong? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6074: postgresql service script
On Thu, Jun 23, 2011 at 4:52 AM, Tom Lane t...@sss.pgh.pa.us wrote: I'm not entirely sure that the OP is using the RHEL RPMs, though, because the fragment he quoted didn't quite match this. It doesn't look like the script from the installers either. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6006: Will not install
On Thu, May 5, 2011 at 1:51 PM, francis.br...@agfa.com wrote: Good Morning Dave.. Thanks for getting back to me... Please find attached the Dependency Walker files . Having not used this tool before, I hope this is the information you want. I cannot read those files on the Mac I have with me. Can you just tell me if any of the dependent libraries are missing or unusable? They normally show up with a warning icon in the treeview. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6006: Will not install
On Thu, May 5, 2011 at 2:05 PM, francis.br...@agfa.com wrote: Ok... Looking at libubtl.dll there does not appear to be any problem. Looking at initdb.exe It appears to be complaining about IESHIMS.DLL Here is jpg view.. Thanks. ieshims.dll shouldn't be a problem. Still not sure what would cause libintl loading to fail, though I have to wonder if it's something to do with your non-default installation path. Does it work if you install to the default directory? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6006: Will not install
On Thu, May 5, 2011 at 2:39 PM, francis.br...@agfa.com wrote: Thanks Dave! WOW! Really!... Yes that installed ok..but why? I can not have the database installed and running from the C: drive permanently. Just a hunch. What is the drive you were trying to use? How is it mounted, and what is the filesystem on it? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6006: Will not install
On Wed, May 4, 2011 at 10:25 PM, Frank Brown francis.br...@agfa.com wrote: The following bug has been logged online: Bug reference: 6006 Logged by: Frank Brown Email address: francis.br...@agfa.com PostgreSQL version: 9.0.4 Win x64 Operating system: Windows 2008 Server x64 Description: Will not install Details: Initdb.exe - System Error Dialog box. The program can't start because libintl.dll is missing from your computer. Try reinstalling the program to fix this problem. Tried 9.0.2 win x64 version with same results. I have been trying off and on for several days, googleing for similar issues. I have changed the rights on the L:\PostgreSQL and also L:\PostgreSQL\9.0\data to give user postgres full control. The libintl.dll does exist in the L:\PostgreSQL\9.0\bin folder. It also exists with in C:\Users\tatlas\AppData\Local\Temp\2\postgresql_installer during the install process. any help appreciated! Can you see if that DLL is missing any dependencies using the depends tool? (http://www.dependencywalker.com/). -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5800: corrupted error messages (encoding problem ?)
On Tue, Apr 26, 2011 at 10:07 AM, Carlo Curatolo genam...@brutele.be wrote: Just tested the 9.0.4...same problem I am affraid... Uh, that's odd. I've asked someone to see if we can reproduce it again. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5981: Attempt to install language pltcl fails on 64-bit installation
On Fri, Apr 15, 2011 at 2:16 AM, Chris Price cjpr...@bigpond.net.au wrote: The following bug has been logged online: Bug reference: 5981 Logged by: Chris Price Email address: cjpr...@bigpond.net.au PostgreSQL version: 9.0.3 Operating system: Winders Server 2008 R2 Standard Description: Attempt to install language pltcl fails on 64-bit installation Details: When I try to install the pltcl language on 64-bit Windows version of PostreSQL (9.0.3) it fails with the following message: ERROR: could not access file $libdir/pltcl: No such file or directory SQL state: 58P01 ActiveTcl is installed. It works on a 32-bit installation of PostgreSQL. I notice that the file pltcl.dll is not installed in the $libdir folder on the 64-bit installation - is there a reason for this? Is the pltcl language available on 64-bit installations on Windows? If memory serves, there was no win64 TCL distro available when we put together the installers for 9.0, so it was left out. There are now of course, so I'll see about adding support for that for 9.1. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5971: NpgSql link doesnt work
On Mon, Apr 11, 2011 at 9:01 AM, John Taylor kakaoscsig...@gmail.com wrote: The following bug has been logged online: Bug reference: 5971 Logged by: John Taylor Email address: kakaoscsig...@gmail.com PostgreSQL version: 9.0 Operating system: Windows 7 Description: NpgSql link doesnt work Details: Hi! http://npgsql.projects.postgresql.org/ link doesn't work. Please repair it, I'd like to download connector for .net . Thanks a lot. It works fine for me. Intermittent network issue perhaps? Or maybe something blocking your access? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text
On Tue, Mar 22, 2011 at 4:09 PM, Dave Page dp...@pgadmin.org wrote: On Tue, Mar 22, 2011 at 3:45 PM, Dave Page dp...@pgadmin.org wrote: On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco craig.sa...@gmail.com wrote: The following bug has been logged online: Bug reference: 5938 Logged by: Craig Sacco Email address: craig.sa...@gmail.com PostgreSQL version: 9.0.3 Operating system: Microsoft Windows (all variants, 32 and 64 bit) Description: PostgreSQL Installer outputs log file with superuser password in clear text Details: The PostgreSQL installer outputs a log file to the temporary directory with the superuser password in clear text. We are deploying PostgreSQL as part of a commercial product and would like to ensure that the password is not available to ordinary users. This has been fixed for the next releases. For the sake of the archives, it should also be noted that the file is in a secure directory, much as a .pgpass file would be, so this is generally only an issue for the situation described above, and not when a user installs a copy himself. Updated one click installers for 9.0.3 on win32 and win64 and for 8.4.7 on win32 are now available from http://www.postgresql.org/download/windows -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text
On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco craig.sa...@gmail.com wrote: The following bug has been logged online: Bug reference: 5938 Logged by: Craig Sacco Email address: craig.sa...@gmail.com PostgreSQL version: 9.0.3 Operating system: Microsoft Windows (all variants, 32 and 64 bit) Description:PostgreSQL Installer outputs log file with superuser password in clear text Details: The PostgreSQL installer outputs a log file to the temporary directory with the superuser password in clear text. We are deploying PostgreSQL as part of a commercial product and would like to ensure that the password is not available to ordinary users. This has been fixed for the next releases. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #5938: PostgreSQL Installer outputs log file with superuser password in clear text
On Tue, Mar 22, 2011 at 3:45 PM, Dave Page dp...@pgadmin.org wrote: On Tue, Mar 22, 2011 at 5:10 AM, Craig Sacco craig.sa...@gmail.comwrote: The following bug has been logged online: Bug reference: 5938 Logged by: Craig Sacco Email address: craig.sa...@gmail.com PostgreSQL version: 9.0.3 Operating system: Microsoft Windows (all variants, 32 and 64 bit) Description:PostgreSQL Installer outputs log file with superuser password in clear text Details: The PostgreSQL installer outputs a log file to the temporary directory with the superuser password in clear text. We are deploying PostgreSQL as part of a commercial product and would like to ensure that the password is not available to ordinary users. This has been fixed for the next releases. For the sake of the archives, it should also be noted that the file is in a secure directory, much as a .pgpass file would be, so this is generally only an issue for the situation described above, and not when a user installs a copy himself. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #5919: released zipped files have problem
[Please keep the list CC'd] On Mon, Mar 14, 2011 at 8:01 AM, jacob lee jacobswel...@yahoo.com wrote: I don't think it is the msvc++ problem. At first the pgsql was installed successfully with initdb with zip file and I tried to start the pg and I got the message. I thought the problem is in my pc so I format it and tried to install with unzipped files. still the message was the same. And I made a success in windows 7 pc. it has no problem. only the windows xp system. and I tested with 2 pcs. The last try was using one-click installer. I installed pgsql with it and copy all the files and directorys except data and removed the pgsql. and I tried to install another pc with copied program and there was no problem! I think the message was that the program was malfunctioned like when the zip file has broken area in it. The fact that the same file worked on a number of other PCs tells us it's not corrupted. Also, the zip archive contains *exactly* the same files as the installer - they're archives as part of the same build process. The error message you quoted is one that almost always means that the runtimes are not correctly installed (or the version of them is incorrect). I don't know precisely what you did, but I'm sure that somewhere along the line the runtimes were installed properly. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Re: [BUGS] BUG #5922: Add-on installation error.
On Thu, Mar 10, 2011 at 8:44 AM, Luke Gilbert luke.gilb...@navistar.com wrote: The following bug has been logged online: Bug reference: 5922 Logged by: Luke Gilbert Email address: luke.gilb...@navistar.com PostgreSQL version: 9.0 Operating system: Windows 7 Description: Add-on installation error. Details: Of all the lists, this seems to be be the best place to file this. This report is not a bug with PostgreSQL; it is a problem with the installer. In searching the archives, this problem does not appear to have been reported yet. I apologize if I've submitted this to the wrong list. When installing postgresql-9.0.3-1-windows_x64.exe on Windows 7, the installation of PostgreSQL completes successfully. After the installation, I chose to install the edb_apachephp add-on and the edb_phppgadmin add-on. When edb_apachephp.exe is run the bitrock_installer_xxx.log file reported the following (some parts redacted): - begin - Preferred installation mode : qt Trying to init installer in mode qt Mode qt successfully initialized Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\EnterpriseDB\ApachePhp APACHE_PORT. Setting variable apacheport to empty value Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\EnterpriseDB\ApachePhp APACHE_HOME. Setting variable apache_home to empty value Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\EnterpriseDB\ApachePhp Branding. Setting variable iBranding to empty value Using branding: Postgres Plus Add-ons Executing C:\Users\\AppData\Local\Temp\vcredist_x86.exe /Q Script exit code: 3010 Script output: Script stderr: Program ended with an error exit code Error running C:\Users\\AppData\Local\Temp\vcredist_x86.exe /Q : Program ended with an error exit code - end - To fix this, I located vcredist_x86.exe and ran it as Administrator. I was given two options: 'Repair' and 'Uninstall'. I chose 'Repair'. Once vcredist_x86.exe completed, I rebooted. After the reboot, I re-ran edb_apachephp.exe and it completed successfully. Unfortunately that's a Microsoft installer, and there's not much we can do about the way it decides to throw an error. It seems like in this case, it decided it couldn't do the normal upgrade to whatever version you had installed already (which may have been the same one, but that doesn't normally matter), and instead decided to throw an error and force you to run a Repair. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5919: released zipped files have problem
On Tue, Mar 8, 2011 at 1:32 AM, Jacob Lee jacobswel...@yahoo.com wrote: The following bug has been logged online: Bug reference: 5919 Logged by: Jacob Lee Email address: jacobswel...@yahoo.com PostgreSQL version: 9.0.3 Operating system: windows XP Description: released zipped files have problem Details: the oneclick installer version has no problem but the zip file has problem. you can find the problem by doing: 1. download the zip file and unzip. 2. try to initdb the system will give the message the application has problem and try to reinstall it. I've tested serval times. I solved the problem doing this: install pgsql by onclick installer and copy all files to where I want. You installed the MSVC++ runtimes first? They're not included in the zip file if memory serves. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
