> On 5 Oct 2013, at 13:21, Michael Paquier wrote:
>
>> On Fri, Oct 4, 2013 at 11:36 AM, Paragon Corporation 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
sion 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.bl
670
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 Enterpris
e
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@postgresq
f postgresql!!
PostgreSQL 8.4.x is not supported on Windows 2012 (and 8.4.0 shouldn't
be used anywhere any more). You need to use 9.2.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-
> 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
En
e 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.or
On Fri, Mar 22, 2013 at 11:58 AM, Marcelo Matheus
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.
--
Da
ion 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: @pgsna
d 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
ve 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
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
e 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
ersions (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@pos
ing 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
E
it in a regular command prompt, and one opened
using the "Run As Administrator" option.
If you see something different from the message above it may help to
remove the "On Error Resume Next" lines from the script and run it
again. That should give additional error detail that th
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=%SystemRoo
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
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
--
On Fri, Jan 4, 2013 at 4:35 PM, Aleksander Shniperson
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.enterpr
t run uninstall
>
> 04.01.2013, в 20:18, Dave Page написал(а):
>
>> On Fri, Jan 4, 2013 at 3:43 PM, Aleksander Shniperson
>> wrote:
>>> Sorry.
>>>
>>> It does not fix the problem.
>>>
>>>> /Library/pgAgent
>>> path not exi
rsion 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@postgres
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:/
ot;/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 Co
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.
--
se 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
s 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
gt;>>
>>>>>> 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
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
> explains that --serviceaccount postgres can be used on the command line.
>
> Should I go on this way?
>
Only if you have a specific need to use a different service account (you'll
know if that's the case for you). For the vast majority of people,
NetworkService should be
On Fri, Sep 14, 2012 at 10:09 AM, Tom Lane wrote:
> Dave Page writes:
>> On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar
>> 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
git;a=commit;h=d5a7bf8c11c8b66c822bbb1a6c90e1a14425bd6e
On Fri, Sep 14, 2012 at 6:54 AM, Dave Page wrote:
> On Fri, Sep 14, 2012 at 6:14 AM, Sandeep Thakkar
> wrote:
>> No.. what I mean to say is that the output from getlocales is same in 9.1
>> and 9.2. (I checked the installatio
quot; -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&qu
;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.blogs
e0a3b8204ce0cdd21564f23d5df;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 subscr
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 t
ar 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
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
On Thu, Aug 16, 2012 at 3:28 PM, Dave Page wrote:
> On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane wrote:
>> Dave Page 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
&g
On Thu, Aug 16, 2012 at 3:26 PM, Tom Lane wrote:
> Dave Page 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 poss
On Wed, Aug 15, 2012 at 2:43 PM, Dave Page wrote:
> On Wed, Aug 15, 2012 at 2:37 PM, Rikard Pavelic
> 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:
>>
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
>> installatio
On Mon, Aug 13, 2012 at 1:57 PM, Heikki Linnakangas
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
>> install
nd 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://p
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
On Mon, Aug 13, 2012 at 7:22 AM, Heikki Linnakangas
wrote:
> On 09.08.2012 17:55, Dave Page wrote:
>>
>> On Thu, Aug 9, 2012 at 3:51 PM, Heikki Linnakangas
>> wrote:
>>>
>>> On 09.08.2012 17:07, kargor wrote:
>>>>
>>>>
>>>
gger 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.
X
>> >
>> > 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 o
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
/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
Enterp
On Fri, Jul 6, 2012 at 9:38 AM, Dave Page wrote:
> On Fri, Jul 6, 2012 at 9:29 AM, wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 6721
>> Logged by: Peter Arnold
>> Email address: peter.arn...@jd-ag
.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 director
On Wed, Jun 27, 2012 at 7:25 AM, Craig Ringer 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 fi
s 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.
On Mon, Jun 25, 2012 at 4:38 PM, Craig Ringer wrote:
> On 06/25/2012 11:10 PM, Dave Page wrote:
>
> On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer wrote:
>
> Dave: Is there any chance the installers link to that page from their error
> dialogs, or a static-and-sanitised version
ude 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:
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_
he
> 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
Sachin, please investigate ASAP.
Thanks.
On Mon, Jun 11, 2012 at 6:30 AM, Edmund Horner wrote:
> On 9 June 2012 03:48, Dave Page wrote:
>> On Fri, Jun 1, 2012 at 1:39 AM, Edmund Horner wrote:
>>> On 1 June 2012 12:36, Edmund Horner wrote:
>>>> On 1 June 20
ortunately 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&#x
posed 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.
res":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 workin
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
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
_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 Ente
'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://pg
is even multiarch).
>
> It would be ok if the installer issues a warning - but refusing the install
> outright feels strange...
>
>
This is intentional - amongst other things, it would double the number of
platforms on which we'd have to QA the 32 bit PG and addon installers
On Mon, Jan 30, 2012 at 7:49 AM, Eric Borts wrote:
> On 1/29/2012 3:02 AM, Dave Page wrote:
>>
>> On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal
>> wrote:
>>>
>>>
>>> Nice analysis Eric. ANy idea why (which program set this) this particu
s 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
Ent
12 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,
On Wednesday, October 5, 2011, Thomas Kellerer 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
On Wednesday, October 5, 2011, Craig Ringer 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 i
o 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
On Mon, Oct 3, 2011 at 2:15 PM, Dave Page wrote:
> On Mon, Oct 3, 2011 at 9:42 AM, Thomas Kellerer 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
ete
> 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: @p
On Mon, Oct 3, 2011 at 9:42 AM, Thomas Kellerer 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 o
ia
> 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,
l 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
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 Devar
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 Postgr
allers 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 t
y 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 (pgsq
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 havin
or
> 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 pg
On Tue, Aug 16, 2011 at 8:24 PM, Dave Page wrote:
> On Tue, Aug 16, 2011 at 8:11 PM, Josh Kupershmidt wrote:
>> On Mon, Aug 15, 2011 at 11:31 PM, Kyle Fox wrote:
>>
>>> I used the installer to install Postgres 9.0 on my Mac, and now every 10
>>> seconds a dialo
lved).
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@postgr
t; 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
> u
d. 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: unkn
ported (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
e | 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-
On Thu, Jun 23, 2011 at 4:52 AM, Tom Lane 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://p
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.po
t 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.ent
ith 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
--
n 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/).
--
D
this problem can be fixed with a simple install
> of a new release ?
> Or do I have to reinstall everything ?
> Do I have to wait a release without this problem ?
So you're saying it works for you now in PostgreSQL and pgAdmin?
I can't help with Java apps or dbVisualizer I'm afr
On Tue, Apr 26, 2011 at 10:07 AM, Carlo Curatolo 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.ent
On Tue, Mar 22, 2011 at 7:07 AM, genamiga wrote:
> I tried with 9.0.3...same problem...
This should be resolved in 9.0.4 btw.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pg
s? 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.
--
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
so
1 - 100 of 449 matches
Mail list logo
