Neil Conway <[EMAIL PROTECTED]> writes:
> Right; my question is why we do that. What purpose does it serve to
> install a script that has no hope of working on this particular
> platform?
So we can get bug reports?
In this case the bug report has to be directed elsewhere, but I see
no point in
On 23-Apr-04, at 10:37 PM, Tom Lane wrote:
We install ipcclean on all platforms whether it functions or not.
Right; my question is why we do that. What purpose does it serve to
install a script that has no hope of working on this particular
platform?
-Neil
---(end of bro
Neil Conway <[EMAIL PROTECTED]> writes:
> % ipcclean --version
> /Users/neilc/local/pgsql-cvs/bin/ipcclean: line 114: ipcs: command not
> found
> This machine is running a pretty standard install of OSX 10.3.3.
OSX's support of SysV IPC verges on the brain-dead. I suggest filing a
bug report wi
Bom Dia,
I ran into that trouble too. But as I used Postgresql since 7.0.2, I returned to
the traditional way of doing things as I thought it was due to a wrong
understanding from my part of this issue).
(I presume your PGDATA directory is in /var/lib/pgsl/data and it is run by a
user named 'post
Using a fresh checkout from CVS HEAD, I get the following on my machine:
% ipcclean --version
/Users/neilc/local/pgsql-cvs/bin/ipcclean: line 114: ipcs: command not
found
This machine is running a pretty standard install of OSX 10.3.3.
At the very least, we shouldn't bother installing ipcclean
Hi,
I´m using PostgreSql version 7.3.6 and I get the following error:
java.sql.SQLException: ERROR: Tuple is too big: size 8152, max size 8136
I searched in the Internet and found out that bug was fixed in version 7.2, but I
still get this error.
Any idea and possible solutions?
