Nikolay Hristov ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
pg_clog files problem
Long Description
I am running PostgreSQL 7.2.1 distributed with cygwin on
Windows NT4 SP6.
The data directory is on NTFS drive.
I performed t
[EMAIL PROTECTED] writes:
> I am running PostgreSQL 7.2.1 distributed with cygwin on
> Windows NT4 SP6.
7.2.1 has known bugs; why are you not testing 7.2.3?
> The data directory is on NTFS drive.
Not sure that we can do much about an inherently unreliable platform
:-(. I do not know whether cyg
Sorry for this being so long but I want to describe this as thoroughly as possible.
I am having two problems with foreign keys. One is a performance problem and the
other is a deadlock problem but they are related to the same root cause. I am
running PostgreSQL 7.3 (the released version).
I
On Tue, 10 Dec 2002, Brian Walker wrote:
> As a test I went into "backend/utils/adt/ri_triggers.c" and removed
> the "FOR UPDATE OF X" from the foreign key checks and the concurrency
> issues disappeared. This still make check 1 happen but removed the
> safety net of check 2.
Right, at which poi
Ok, I tested this out with TLSv1 and it worked fine. I found that the
same mistake was being made on the client side of things too so I
included a patch for that too.
--Nate
Index: src/backend/libpq/be-secure.c
===
RCS file:
I am glad you found out the cause of your problems.
I am reluctant to apply this patch because the original author
recommended TLSv1 specifically because it was more secure, especially
compared to SSLv2.
There was a conscious decision in 7.3 to require only 7.3 clients when
using SSL. I don't
JMM ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
initdb fails on an ext2/3 fs mounted on /var/lib/pgsql/data
Long Description
If a whole filesystem (eg a whole disk in one filesystem that is dedicated to postgres
data) is mo
> There was a conscious decision in 7.3 to require only 7.3 clients when
> using SSL. I don't remember how many people were involved in that
> discussion, but I know it was made. In fact, there was so much new SSL
> code in 7.3, I suspected we couldn't even make it work with pre-7.2
> clients. I am
OK, I can apply this. One question I have is why the double strerror()
in the first patch chunk. Also, I will need to manually patch this
because your system has formatted the code quite unusually:
> libpq_g-
>
Ick, my email client wrapped that really weird. That's why the
double strerror is there too -- the first one should be part of the
previous line.
I've found that you can still get the server to crash in the other
error cases or when SSL_read/write returns -1. Since that happens
whenever you try to
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Roland Karch wrote:
> Hello together,
>
[EMAIL PROTECTED] writes:
> If a whole filesystem (eg a whole disk in one filesystem that is
> dedicated to postgres data) is mounted on data location (typically
> /var/lib/pgsql/data), initdb files besause of the existence of the
> lost+found directory in the filesystem root.
> There is an easy b
Can we free only the plans we want to free in geqo? I don't mind having
a different free method in geqo vs. the rest of the optimizer.
---
Tom Lane wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
> > [ GEQO doesn't work any
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Can we free only the plans we want to free in geqo? I don't mind having
> a different free method in geqo vs. the rest of the optimizer.
GEQO calls "the rest of the optimizer", and the space that we're
worried about is almost all allocated in "the rest
Good day to all, It forgives for the bad English,
I use MS Visual FoxPro 6 and am writing an application using the BD PostGreSQL version 7.2.3, but I am finding problems of communication between the Fox and the ODBC (version 7.02.0004), when I create one view that it uses calculated fields of the n
OK, I wonder if adding -ldl will help. You need to link to the library
containing the ldopen function.
---
Shibashish wrote:
> Thanks for the help. I edited the src/makefiles/Makefile.sco and removed
> the export. But the c
16 matches
Mail list logo
