On Tuesday 16 November 2004 21:06, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > I believe that the checks in src/backend/libpq/be-secure.c:653 should be
> > performed in a different order (first the access permissions and then the
> > owner of t
Hi there,
PostgreSQL 7.4.6 gives the following error message when trying to read the
private key in the case of:
-rw--- 1 root root 887 Aug 19 15:01 /var/lib/postgres/data/server.key
2004-11-13 13:04:42 [4095] FATAL: unsafe permissions on private key file
"/var/lib/postgres/data/server.k
On Tuesday 26 October 2004 05:08, Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Please consider changing the default for IRIX systems to select() instead
> > of poll().
>
> Can you suggest a test for configure to determine that poll() is broken?
> I'm not particularly exc
On Friday 20 August 2004 03:52, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > It seems that the problem is in src/template/linux:
> >
> > $ cat src/template/linux=20
> > # Force _GNU_SOURCE on; plperl is broken with Perl 5.8.0 othe
On Wednesday 18 August 2004 23:09, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > This happens because AC_CHECK_HEADERSis implemented using the
> > preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
>
> The correct variable is CPPFLAGS. Actually, you
On Wednesday 18 August 2004 20:14, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > It seems that you've removed the possibility to add an argument to
> > --with-openssl option of the configure script. Currently I'm
> > maintaining two systems where the
Hi there...
I'm trying to compile pgsql 8.0.0b1.
It seems that you've removed the possibility to add an argument to
--with-openssl option of the configure script. Currently I'm maintaining two
systems where the openssl is not somewhere in the standard paths and thus the
only way to compile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 07 February 2003 02:03, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > I'm stuck here with a query that kills postgresql backend.
>
> Hoo, that was a fun one. Try this patch ...
First I t
I'm stuck here with a query that kills postgresql backend.
I've installed postgresql 7.3.1 on two machines..
one with gcc 3.2, glibc 2.3.1 source based (a)
and the other with gcc 2.95.3, glibc 2.2.3 slackware 8 (b)
both are PIII with kernel 2.4.20.
(a) has ext3 and (b) has xfs for the database st
I'm running postgresql 7.2.1 on linux.
I cannot run vacuumm on a table in a database i'm running for about 7 months.
I get:
ERROR: No one parent tuple was found
I've found an older posting about that but the poster said that after
restarting it was fixed. In my case this is not true. I've rest
10 matches
Mail list logo
