This just so that somebody looking for TODO items in the source can find
this one too.
Regards,
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] gmail | hotmail | yahoo }.com
TODO.patch
Description: Binary data
---(end of broadcast)---
TIP 7: You can
Gurjeet Singh wrote:
cd pgsql/doc/src/sgml
make html
See
http://developer.postgresql.org/pgdocs/postgres/docguide-build.html
http://developer.postgresql.org/pgdocs/postgres/docguide-build.html
This, obviously, isn't working on MinGW for me. I'll try Linux (Ubuntu).
I uninstalled postgresql, removed the 5 files mentioned above from
system32. When I installed 8.2.0 again, the installer reported that
The installer has detected an incompatible version of OpenSSL
installed in your system PATH. PostgreSQL requires OpenSSL 0.9.7 or
later. If you remove your
Knut P. Lehre wrote:
I uninstalled postgresql, removed the 5 files mentioned above from
system32. When I installed 8.2.0 again, the installer reported that
The installer has detected an incompatible version of OpenSSL
installed in your system PATH. PostgreSQL requires OpenSSL 0.9.7 or
later.
Hi,
I've just read most of that thread and found it rather disappointing.
I'd just like to add my 2 (or 3) cents:
a) I like to have the freedom to choose what software (under which
licenses) I'm using. Thus I'd like to see GNUTLS supported, as it adds
an additional feature to PostgreSQL per
On Sun, Dec 31, 2006 at 03:25:42PM +0100, Markus Schiltknecht wrote:
b) The other features of Martijn's patch got completely overseen. Can we
(can you Martijn?) break up the patch into smaller pieces and discuss
single independent features, like querying for parameters of the SSL
On Sun, Dec 31, 2006 at 03:59:29PM +0100, Martijn van Oosterhout wrote:
Please read the OpenSSL-GPL FAQ. They themselves acknowledge it's a
problem, but claim they fall under the operating system exception,
which is fine for everyone except the distributor of the operating
system.
It seems your interpretation of the OpenSSL position is as
questionable as your interpretation of the GPL, and what the GPL can
legally require. :-)
Nobody has proven an issue exists. The only way to prove it would be
for an actual court case to set the precident.
Further, OpenSSL is not
Hi,
Martijn van Oosterhout wrote:
Please read the OpenSSL-GPL FAQ. They themselves acknowledge it's a
problem, but claim they fall under the operating system exception,
which is fine for everyone except the distributor of the operating
system.
http://www.openssl.org/support/faq.html#LEGAL2
Tom Lane wrote:
Seneca Cunningham [EMAIL PROTECTED] writes:
I don't have a core, but here's the CrashReporter output for both
of jackal's failed runs:
Wow, some actual data, rather than just noodling about how to get it ...
thanks!
...
11 postgres 0x0022b2e3
Hi,
[EMAIL PROTECTED] wrote:
Nobody has proven an issue exists. The only way to prove it would be
for an actual court case to set the precident.
That's exactly the mentality that I'm questioning. Why always go to
legal boundaries and ask for courts?
Joshua D. Drake wrote:
Further, OpenSSL
Gurjeet Singh [EMAIL PROTECTED] writes:
The comment above TOAST_INDEX_HACK in tuptoaster.h is:
/*
* This enables de-toasting of index entries. Needed until VACUUM is
* smart enough to rebuild indexes from scratch.
*/
#define TOAST_INDEX_HACK
Do we already have a TODO item to remove
Gurjeet Singh [EMAIL PROTECTED] writes:
This just so that somebody looking for TODO items in the source can find
this one too.
If you're looking for TODO items, why wouldn't you be looking in the
TODO document?
regards, tom lane
---(end of
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
fwiw - I can trigger that issue now pretty reliably on a fast Opteron
box (running Debian Sarge/AMD64) with make regress in a loop - I seem to
be able to trigger it in about 20-25% of the runs.
the resulting core however looks totally stack
On Sun, Dec 31, 2006 at 05:43:45PM +0100, Stefan Kaltenbrunner wrote:
Tom Lane wrote:
What you seem to have here is infinite recursion during relcache
initialization. That's surely not hard to believe, considering I just
whacked that code around, and indeed changed some of the tests that
Hi,
http://archives.postgresql.org/pgsql-committers/2005-11/msg00183.php
this one removes the original algorithm name of access method from
create_index.sqml. why?
was that readded somewhere else?
--
regards,
Jaime Casanova
Programming today is a race between software engineers striving to
On Thu, 21 Dec 2006 10:47:52 -0500
Tom Lane [EMAIL PROTECTED] wrote:
One bug I see in it is that you'd better make the alignment 'd' if the
type is to be int8. Also I much dislike these changes:
- int32 i = PG_GETARG_INT32(1);
+ int64 i = PG_GETARG_INT32(1);
I
Jaime Casanova [EMAIL PROTECTED] writes:
http://archives.postgresql.org/pgsql-committers/2005-11/msg00183.php
this one removes the original algorithm name of access method from
create_index.sqml. why?
It wasn't complete, up-to-date, or particularly helpful in context.
was that readded
On 12/31/06, Tom Lane [EMAIL PROTECTED] wrote:
Gurjeet Singh [EMAIL PROTECTED] writes:
The comment above TOAST_INDEX_HACK in tuptoaster.h is:
/*
* This enables de-toasting of index entries. Needed until VACUUM is
* smart enough to rebuild indexes from scratch.
*/
#define
The comment, This should be improved someday sure sounds like a TODO to
me.
I don't know if it should make it to the TODO doc, as that lists
high-level/abstract feature-request-like items.
Probably I should stop acting on impulse here. Hey, can someone around here
lend me his rock!! ( no
20 matches
Mail list logo
