On Thursday 02 July 2009 09:56:35 Peter Eisentraut wrote:
> On Thursday 02 July 2009 02:45:24 John R Pierce wrote:
> > ajmcello wrote:
> > > The only downside with adding o to tar that I can see is if it isn't
> > > supported by a non-GNU version of tar.
> >
> > On solaris 9 and 10 at least, tar -o
On Thursday 02 July 2009 02:45:24 John R Pierce wrote:
> ajmcello wrote:
> > The only downside with adding o to tar that I can see is if it isn't
> > supported by a non-GNU version of tar.
>
> On solaris 9 and 10 at least, tar -o means set ownership of extracted
> files to the runner and not the ui
On 07/02/2009 09:17 AM, 刘鑫 wrote:
system : windows xp Chinese simple
postgres : postgresql-8.4.0-1-windows.exe
installl processing and errors:
install failed by one click installer, then I run initdb.
Can you please post the error part in the install logs present in your
system's temp direct
Peter Schuller wrote:
> > >> What generic error?
> >
> > > Error: Invalid line 496 in /etc/postgresql/8.3/main/postgresql.conf:
> > > »include 'filename' « failed!
> >
> > > This is with a Debian PostgreSQL 8.3.
> >
> > There is no such error message in Postgres 8.3 (or any other version).
>
?? wrote:
> system : windows xp Chinese simple
> postgres : postgresql-8.4.0-1-windows.exe
> F:\PostgreSQL\8.4\bin>initdb -U postgres --encoding=utf8 --locale=utf8
It's not a bug, just "utf8" is not a valid locale name.
Use the following instead:
$ initdb --encoding=UTF8 --locale="Chinese (Simp
system : windows xp Chinese simple
postgres : postgresql-8.4.0-1-windows.exe
installl processing and errors:
install failed by one click installer, then I run initdb.
F:\PostgreSQL\8.4\bin>initdb -U postgres --encoding=utf8 --locale=utf8
--lc-coll
ate='missing' F:\PostgresSQL\8.4\data
initdb: in
Peter Schuller wrote:
-- Start of PGP signed section.
> > >> What generic error?
> >
> > > Error: Invalid line 496 in /etc/postgresql/8.3/main/postgresql.conf:
> > > ??include 'filename' ?? failed!
> >
> > > This is with a Debian PostgreSQL 8.3.
> >
> > There is no such error message in Postgre
ajmcello wrote:
The only downside with adding o to tar that I can see is if it isn't
supported by a non-GNU version of tar.
On solaris 9 and 10 at least, tar -o means set ownership of extracted
files to the runner and not the uid in the tar, which I assume is what
we want here.
Note, this
Bruce Momjian writes:
> Tom Lane wrote:
>> It's required by the Single Unix Spec
>> http://www.opengroup.org/onlinepubs/007908799/xcu/tar.html
>> (although that specifically disallows the ordering "oxf" that you
>> suggest) and I see it in tar on HPUX 10.20, which ought to be about
>> ancient enou
Tom Lane wrote:
> ajmcello writes:
> > The only downside with adding o to tar that I can see is if it isn't
> > supported by a non-GNU version of tar.
>
> It's required by the Single Unix Spec
> http://www.opengroup.org/onlinepubs/007908799/xcu/tar.html
> (although that specifically disallows the
The following bug has been logged online:
Bug reference: 4897
Logged by: Gerhard Leykam
Email address: gel...@sealsystems.de
PostgreSQL version: 8.3.7.1
Operating system: Windows Server 2003 SP2
Description:PostgreSQL 8.3.7 crashes on Win2003 logoff
Details:
Hi!
Th
> >> What generic error?
>
> > Error: Invalid line 496 in /etc/postgresql/8.3/main/postgresql.conf:
> > »include 'filename' « failed!
>
> > This is with a Debian PostgreSQL 8.3.
>
> There is no such error message in Postgres 8.3 (or any other version).
> I speculate that you are dealing with
12 matches
Mail list logo
