Tom Lane wrote:
What is important is that it is possible, and useful, to build Postgres
in a completely non-GPL environment. If that were not so then I think
we'd have some license issues. But the fact that building PG in a
GPL-ized environment creates a GPL-ized binary is not a problem from m
[EMAIL PROTECTED] wrote:
We do not want to open up the BSD vs GPL debate, but keeping PG as a BSD
license does take an amount of accounting.
I was using GPL as an example, as it was mentioned earlier in the
thread. My comments hold for *any* license, including (at least in the
UK; unfair contract
[EMAIL PROTECTED] wrote:
I'm probably just being alarmist, but think about some IP lawyer buying up
the entity that owns the GPL code, and suing end user's of PostgreSQL.
You cannot retrospectively change the terms of a license unless the
licensee agrees to it. If something is released GPL, then t
sdv mailer wrote:
> We used to run persistent connection until the DB
> servers got maxed out because of too many idle
> connections sucking up all the memory. Web servers run
> different loads than database servers and persistent
> connections are notorious for crashing your DB.
And this translat
Rob Butler wrote:
> $369 for 4GB of storage in a compact flash card is not all that bad.
> $189 for 2.2GB is very reasonable when you consider the 512MB CF is
> going for $149!
The current "cheap" workaround to get a Hitachi (ne IBM) 4GB microdrive is
to buy a Creative Muvo2 4GB and open it up to
Bruno Wolff III wrote:
The context of my suggestion was for recovering up until a transaction which
messed things up was committed. I did not want the problem transaction to
be committed. If the problem transaction ran for a long time, there might
be other transactions that I want to keep, if possi
Bruno Wolff III wrote:
For long running transactions where you want to recover as much as possible,
one might also want to recover up until just before a specific transaction
committed (as opposed to started).
If your DB has died and you are recovering it, how do you reestablish a
session so that
Jan Wieck wrote:
> 2PC is not too slow in normal operations when everything is purring
> like little kittens and you're just wasting your excess bandwidth on
> it. The point is that it behaves horrible and like a dirty backstreet
> cat at the time when things go wrong ... basically it's a neat thin
Sean Chittenden wrote:
> To prevent lib naming collisions with machines that have libevent
> installed, I plan on renaming all of the functions from event_* to
> pgevent_*. libevent also has the appropriate autoconf goo to make
> detection of the right library pretty seamless. It even supports th
> 1. the userid isn't deleted or anything like that.
>
> 2. validuntil is only checked in password authentication methods; if you
> are able to connect via a non-password auth method (eg IDENT) then it's
> not checked.
>
> I've never been quite sure whether #2 is a bug or a feature, though.
Withou
be in time for the 7.3 release ?
rgds,
--
Peter
- Original Message -----
From: "Peter Galbavy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, November 05, 2002 8:13 AM
Subject: openbsd 3.2, postgresql 7.3beta3 and openssl 'e_os.
moving to release later when we are ready to
test final work.
Also, would it be possible to announce alpha/beta/RC releases to
pgsql-announce ?
rgds,
--
Peter Galbavy
Knowledge Matters Ltd
http://www.knowledge.com/
---(end of broadcast)---
TIP 5
raditional 'net environment.
As we are coding various other stuff for this project over the next few
months, any help we can be in developing for this part of PostgreSQL, just
let me know. While knowing very little about PostgreSQL internals, we learn
quick.
rgds,
13 matches
Mail list logo
