Re: [ADMIN] strange error

2007-07-05 Thread De Leeuw Guy
Hello I match the problem : a trigger writed in PL::Ruby If I remove the trigger ok. but I don't know how fix it. De Leeuw Guy a écrit : > Hello, > > I try to copy a file into a database : > On our main server (postgresql 8.1 debian etch ia64) no problem. > On a test laptop (postgresql 8

[ADMIN] strange error

2007-07-05 Thread De Leeuw Guy
Hello, I try to copy a file into a database : On our main server (postgresql 8.1 debian etch ia64) no problem. On a test laptop (postgresql 8.2 debian testing lenny ia32) I receive the error : the size of the array exceed the maximum allowed (268435455) db_stats=# COPY table_cat FRO

[ADMIN] Strange error on start up on a RH9 system - Help Please

2004-01-26 Thread Kevin Verma
Hello Every one, I have a local server here and this is what's happening: [EMAIL PROTECTED] root]# service postgresql start Starting postgresql service: su: incorrect password [FAILED] I am able to do perform all the actions manually on command line but not with postgresql init script. Please h

Re: [ADMIN] Strange error message

2001-08-27 Thread Tom Lane
[EMAIL PROTECTED] writes: > Problem is that vacuum still failed with an out of disk space > message. Anyone knows on how much a table needs to be vacuumed correctly ? > (A 20GB table with 4GB indexes did not vacuum in 50GB of free space). Update to 7.1.3, or apply the patch that was posted back

Re: [ADMIN] Strange error message

2001-08-26 Thread Robert . Farrugia
L PROTECTED] Subject: Re: [ADMIN] Strange error message 19/08/2001

Re: [ADMIN] Strange error message

2001-08-19 Thread Tom Lane
[EMAIL PROTECTED] writes: > FATAL 2: InitRelink(logfile 347 seg 167) failed: Operation not permitted Looks like a permissions problem in the pg_xlog directory. Is that directory owned and writable by the postgres user? > The setup is as follows, the pg_xlog is situated on another PC (win > 200

[ADMIN] Strange error message

2001-08-19 Thread Robert . Farrugia
Hi to all, During a vacuum, the message below appeared after some time doing the command. FATAL 2: InitRelink(logfile 347 seg 167) failed: Operation not permitted /usr/bin/postmaster: Startup proc 22070 exited with status 512 - abort The postmaster bombs out, and when trying to reinit, it give

[ADMIN] Strange error

1999-12-21 Thread Andy Lewis
I have a problem. First I had a drive error that I corrected and when I do a vacuum, I get the following: mydb=> vacuum; ERROR: OperatorObjectIdFillScanKeyEntry: unknown operator 93 Anyone know what I am susposted to do? I haven't the slightest idea of how to correct this one. Thanks Andy