The umlaut problem is a known issue in the current installer. I beleive we have
a solution for it committed, and we're currently testing that one.
As for the actual translation, I'll leave that one to Harald (he does the
german translation).
Finally, please post comments about the installer to
> The following bug has been logged online:
>
> Bug reference: 1357
> Logged by: Winfried Maus
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows Server 2003
> Description:Installation via Terminal Service
> Details:
>
> When try
Zitat von Michael Fuhr <[EMAIL PROTECTED]>:
>> This is exactly what I did fix with the work mentioned in the hackers
>> thread. It should work nicely with CVS HEAD. Could you please try
>> this?
>
> Try what? I don't see a patch, link, or suggested fix in the
> thread -- just your original messag
Here is (was) the problem. I was working in an
administrator account. Not Root, but an admin account.
This is the first time that OS X choked while working
this way. RC1 was fine so something else must have
really changed.
Anyway, I just created a 'standard' user, moved the
folder and did the ma
The one thing I didn't think about is that standard
users cannot sudo. So now I need to figure out how to
create a 'standard' user with privs high enough to
sudo to install.
Ted
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Theodore Petrosky <[EMAIL PROTECTED]> writes:
> > I just found the time to t
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> Here is (was) the problem. I was working in an
> administrator account. Not Root, but an admin account.
That seems a bit hard to believe.
Looking back at your original message, I notice something that escaped
me the first time: the actual failure me
Tom,
the full path was:
/Users/asacksadmin/Documents/postgresql-8.0.0rc2
this is where the source lived and where I issued the
./configure --with-xxx and yyy
make
make check //which failed
sudo make install
there are no spaces in the path..
interesting on a different note Ab :)
I wan
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> the full path was:
> /Users/asacksadmin/Documents/postgresql-8.0.0rc2
Really? What I see at
http://archives.postgresql.org/pgsql-bugs/2004-12/msg00263.php
definitely looks like
/Users/postgres/Documents/postgresql
source/postgresql-8.0.0rc2/src/te
that's correct, that was the computer at home at that
does have the space in the path..
however my machine in the office that had the
identical problem has no spaces and is the machine
that I used to create the standard user.
Sorry about that, I tend to run around a lot and work
on different mach
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> that's correct, that was the computer at home at that
> does have the space in the path..
> however my machine in the office that had the
> identical problem has no spaces and is the machine
> that I used to create the standard user.
Your machine in
You are right..
I started over from untarring the source and
everything worked. I must have just done a make clean
and it didn't like something.
Just to reiterate
i untarred the distro
./configure --with-rendezvous --enable-thread-safety
make
make check
everything is ok my bad... mea
The following bug has been logged online:
Bug reference: 1367
Logged by: Hong Yuan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows XP Chinese Simplified
Description:Unique constraint fails with some values
Details:
I found that the
"Hong Yuan" <[EMAIL PROTECTED]> writes:
> I found that the unique constraint fails sometimes when the varchar column
> contain some specific Chinese characters. Here is an example:
The usual cause of this sort of thing is that you've selected a database
encoding that is not compatible with the loc
13 matches
Mail list logo
