Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
This is *not* going in the right direction :-(
Well, then show me what direction you think is better.
Fewer restrictions, not more. The thrust of what I've been saying
(and I think Roman too) is to trust in the hardware float-arithmetic
On 12/29/06, Stephen Frost wrote:
So, Debian is distributing an application (exim4 w/ libpq libssl)
which includes GPL code (exim4) combined with code under another license
(BSD w/ advertising clause) which *adds additional restrictions* (the
advertising clause) over those in the GPL, which is
Hello,
I can see : WITH RECURSIVE hierarchical queries (Jonah H. Harris) in :
http://developer.postgresql.org/index.php/Todo:WishlistFor83
GREAT!!!
Such feature is very important, because it is supported in most of
commercial database
SQL Server 2003 support WITH RECURSIVE
DB2 support it too
JCN == Jim C Nasby [EMAIL PROTECTED] writes:
JCN Truth is, I bet many (if not most) DBAs barely know that case
JCN matters in the units.
Sounds like the school system needs fixing, then.
/Benny
---(end of broadcast)---
TIP 7: You can help
On Fri, Dec 29, 2006 at 12:08:37AM -0500, Tom Lane wrote:
Stephen, let me explain *exactly* why I think this is horsepucky.
libjpeg, my other major open-source project, has always been shipped
under a BSD-ish license that includes an advertising clause; I quote:
: (2) If only executable
On Thu, Dec 28, 2006 at 10:52:45PM -0500, Bruce Momjian wrote:
Edwin Ramirez wrote:
Hello,
What is the status of supporting the WITH keyword?
I see these TODO items:
* Add SQL99 WITH clause to SELECT
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Are
Just a freshing for clean applying..
http://www.sigaev.ru/misc/user_defined_typmod-0.11.gz
Is any objections to commit?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
This is not responding to my concern. What you presented was an
Sorry, I see your point now.
Is that test enough? Or I should make more?
--
Teodor Sigaev E-mail: [EMAIL PROTECTED]
WWW: http://www.sigaev.ru/
* Martijn van Oosterhout (kleptog@svana.org) wrote:
On Fri, Dec 29, 2006 at 12:08:37AM -0500, Tom Lane wrote:
libjpeg, my other major open-source project, has always been shipped
under a BSD-ish license that includes an advertising clause; I quote:
: (2) If only executable code is
On Thu, 2006-12-28 at 21:35 +, Heikki Linnakangas wrote:
I only used 1 bit, just like in Itagaki's approach.
1 bit may not be enough.
In many cases, a block will receive only 1 UPDATE or DELETE. If we then
mark this in the DSM, when we VACUUM that block it will not have
sufficient space
On Fri, Dec 29, 2006 at 08:31:34PM +1300, Mark Kirkwood wrote:
[EMAIL PROTECTED] wrote:
I will try again. It is a difficult subject for many.
GPL software derived from PostgreSQL must honour the restrictions defined
by the PostgreSQL (BSD) license.
GPL software derived from OpenSSL must
On Fri, Dec 29, 2006 at 09:52:08AM -0500, [EMAIL PROTECTED] wrote:
I think the issue revolves around the conditions that GPL stipulates
about linking against libraries requiring the entire product to be
*distributed* as GPL, even if components have differing licenses. This
is the
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
This is *not* going in the right direction :-(
Well, then show me what direction you think is better.
Fewer restrictions, not more. The thrust of what I've been saying
(and I think Roman too) is to trust in the
David Fetter wrote:
On Thu, Dec 28, 2006 at 10:52:45PM -0500, Bruce Momjian wrote:
Edwin Ramirez wrote:
Hello,
What is the status of supporting the WITH keyword?
I see these TODO items:
* Add SQL99 WITH clause to SELECT
* Add SQL:2003 WITH RECURSIVE (hierarchical)
Bruce Momjian [EMAIL PROTECTED] writes:
OK, are you saying that there is a signal we are ignoring for
overflow/underflow, or that we should just silently overflow/underflow
and not throw an error?
Silent underflow is fine with me; it's the norm in most all float
implementations and won't
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
GPL software derived from PostgreSQL must honour the restrictions defined
by the PostgreSQL (BSD) license.
GPL software derived from OpenSSL must honour the restrictions defined
by the OpenSSL license.
You're talking about GPL software as if
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
This is *not* going in the right direction :-(
Well, then show me what direction you think is better.
Fewer restrictions, not more. The thrust of what I've been
Simon Riggs [EMAIL PROTECTED] writes:
I would suggest that we tracked whether a block has had 0, 1 or 1+
updates/deletes against it. When a block has 1+ it can then be
worthwhile to VACUUM it and to place it onto the FSM. Two dead tuples is
really the minimum space worth reclaiming on any
* Martijn van Oosterhout (kleptog@svana.org) wrote:
On Fri, Dec 29, 2006 at 09:52:08AM -0500, [EMAIL PROTECTED] wrote:
We're not talking about including GPL code in OpenSSL, though. This is
about OpenSSL as the base library. The GPL cannot stipulate that a GPL
program may only be linked
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
OK, are you saying that there is a signal we are ignoring for
overflow/underflow, or that we should just silently overflow/underflow
and not throw an error?
Silent underflow is fine with me; it's the norm in most all float
Martijn van Oosterhout kleptog@svana.org writes:
On Fri, Dec 29, 2006 at 12:08:37AM -0500, Tom Lane wrote:
libjpeg, my other major open-source project, has always been shipped
under a BSD-ish license that includes an advertising clause; I quote:
: (2) If only executable code is distributed,
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
here's a quick untested patch for buildfarm that Stefan might like to try.
Note that not all core files are named core. On some Linux distros,
it's configured to be core.PID by default.
I see the above-mentioned files in src/backend/utils/misc. A diff shows
the following:
$ diff postgresql.conf.sample.orig postgresql.conf.sample
223a224
log_destination = 'syslog'
302a304
silent_mode = on
363a366,367
autovacuum = on
What's the purpose of postgresql.conf.sample.orig?
I'm
Bill Moran wrote:
I see the above-mentioned files in src/backend/utils/misc. A diff shows
the following:
$ diff postgresql.conf.sample.orig postgresql.conf.sample
223a224
log_destination = 'syslog'
302a304
silent_mode = on
363a366,367
autovacuum = on
What's the
Andrew Dunstan [EMAIL PROTECTED] writes:
I'm actually wondering if unlimiting core might not be a useful switch
to provide on pg_ctl, as long as the platform has setrlimit().
Not a bad thought; that's actually one of the reasons that I still
usually use a handmade script rather than pg_ctl for
In response to Andrew Dunstan [EMAIL PROTECTED]:
Bill Moran wrote:
I see the above-mentioned files in src/backend/utils/misc. A diff shows
the following:
$ diff postgresql.conf.sample.orig postgresql.conf.sample
223a224
log_destination = 'syslog'
302a304
Bill Moran [EMAIL PROTECTED] writes:
What's the purpose of postgresql.conf.sample.orig?
There is no such file in CVS ... perhaps it's left over from a patch run?
regards, tom lane
---(end of broadcast)---
TIP 6: explain
On Tue, Dec 19, 2006 at 04:58:22PM +0100, Zeugswetter Andreas ADI SD wrote:
MinGW has fseeko64 and ftello64 with off64_t.
Maybe we need separate macros for MSVC and MinGW. Given the other
You mean something quick and dirty like this ? That would work.
Yes,
* Tom Lane ([EMAIL PROTECTED]) wrote:
Martijn van Oosterhout kleptog@svana.org writes:
On Fri, Dec 29, 2006 at 12:08:37AM -0500, Tom Lane wrote:
libjpeg, my other major open-source project, has always been shipped
under a BSD-ish license that includes an advertising clause; I quote:
:
Brian Hurt [EMAIL PROTECTED] writes:
Note that taking a signal on an FP exception is a horribly expensive
proposition- we're talking about hundreds or thousands of clock cycles
here. But it's probably worthwhile vr.s the cost of testing every
floating point result, as generally FP
Now Exim has granted an exception that gets Debian off the hook, but
they didn't have to do that.
Right. If they didn't then it's conceivable that Exim could sue Debian
for violating the GPL license. Not exactly likely to happen but being
cautious it's best to get their explicit approval
The WITH that I am thinking about, lets you define and reuse queries which are executed once. For example:
WITH
MySummary AS (*SELECT b.dept_name, Sum(Salary) AS total_sal FROM emp a join dept b on (a.dept_id = b.dept_id)
GROUP BY b.dept_name*)
SELECT dept_name, total_sal //FROM
On 12/29/06, Stephen Frost wrote:
In the case above, exim4 *can* provide an exception because it's the
*GPL* of *exim4* which is being violated by the advertising clause in
the *OpenSSL* license. Which exim4 upstream has *done*, and which can
be seen in their license (linked to previously in
Magnus Hagander [EMAIL PROTECTED] writes:
Attached patch adds support for the recent XML-in-backend stuff to the
MSVC build. Most config stuff was already present for contrib/xml2, but
needed to add the includes and defines to the backend build as well.
Applied, thanks.
On 12/29/2006 12:23 AM, Bruce Momjian wrote:
Well, then show me what direction you think is better.
Think about this idea please. This has no INF, NaN or range
checks and detects all bad cases with any floating point
math.
The only issue is that a bad case is detected only once.
You need to
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
I'm actually wondering if unlimiting core might not be a useful switch
to provide on pg_ctl, as long as the platform has setrlimit().
Not a bad thought; that's actually one of the reasons that I still
usually use a handmade script
[EMAIL PROTECTED] (Jaime Casanova) writes:
On 12/28/06, Tom Lane [EMAIL PROTECTED] wrote:
Galy Lee [EMAIL PROTECTED] writes:
So I am thinking another way to perform vacuum. For example vacuum can
be refined in a maintenance time frame like VACUUM IN 6 HOURS, and
then vacuum operation will
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
Now Exim has granted an exception that gets Debian off the hook, but
they didn't have to do that.
Right. If they didn't then it's conceivable that Exim could sue Debian
for violating the GPL license. Not exactly likely to happen but being
Caution to the point of fantasy is a waste of resources. Caution to
further a political agenda (not you - but the people whose opinions you
are repeating) is exploitation.
I don't believe Debian has any kind of political agenda in this regard.
Debian's agenda is to follow the licenses
* August Zajonc ([EMAIL PROTECTED]) wrote:
On 12/29/06, Stephen Frost wrote:
In the case above, exim4 *can* provide an exception because it's the
*GPL* of *exim4* which is being violated by the advertising clause in
the *OpenSSL* license. Which exim4 upstream has *done*, and which can
be
On Fri, 2006-12-29 at 10:49 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I would suggest that we tracked whether a block has had 0, 1 or 1+
updates/deletes against it. When a block has 1+ it can then be
worthwhile to VACUUM it and to place it onto the FSM. Two dead tuples is
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
Actually everything about Debian (the project) is a political agenda.
That doesn't mean that it is invalid though.
*smirk
That being said, this topic is WAY OFF-TOPIC for the discussion. The
discussion is:
Will we accept GNU TLS.
Currently
Teodor Sigaev [EMAIL PROTECTED] writes:
Just a freshing for clean applying..
http://www.sigaev.ru/misc/user_defined_typmod-0.11.gz
Is any objections to commit?
There's still a lot I don't particularly care for here (lack of
documentation being the biggest), but I'll make a pass at cleaning it
Roman Kononov [EMAIL PROTECTED] writes:
Think about this idea please. This has no INF, NaN or range
checks and detects all bad cases with any floating point
math.
Doesn't even compile here (no fenv.h).
regards, tom lane
---(end of
On Fri, Dec 29, 2006 at 10:32:34AM -0800, Joshua D. Drake wrote:
Currently there has not been one technical argument that is valid to
have us include GNU TLS.
1) The normal freedom that not being tied down to a single product
provides. The same reason somebody might build MySQL + PostgreSQL
entirely.
4) GNUTLS development seems more active? OpenSSL has been in a frozen/mature
state for a while. I don't understand why OpenSSL is still labelled as
0.9.x, which might indicate alpha quality, under heavy development.
I don't find the reasons too compelling - but they are
On 12/29/2006 11:27 AM, Tom Lane wrote:
Doesn't even compile here (no fenv.h).
Where do you compile?
Roman
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
4) GNUTLS development seems more active? OpenSSL has been in a frozen/mature
state for a while. I don't understand why OpenSSL is still labelled as
0.9.x, which might indicate alpha quality, under heavy development.
I don't find the
On Thu, Dec 28, 2006 at 09:28:48PM +, Heikki Linnakangas wrote:
Tom Lane wrote:
To my mind the problem with fsync is not that it gives us too little
control but that it gives too much: we have to specify a particular
order of writing out files. What we'd really like is a version of
Knut P. Lehre wrote:
Installing postgresql 8.2.0 on Windows XP Pro SP2 using the msi
installer dated 2006-12-04, with libeay32.dll and ssleay32.dll (both
dated 2005-07-06) (and libiconv-2.dll, libintl-2.dll, and libpq.dll)
from a previous installation (of version 8.0.5) already present in
Simon Riggs [EMAIL PROTECTED] writes:
On Fri, 2006-12-29 at 10:49 -0500, Tom Lane wrote:
Counterexample: table in which all tuples exceed half a page.
Current FSM code will ignore those too, if they are less than the
average size of the tuple so far requested. Thats a pretty wierd
Jim C. Nasby [EMAIL PROTECTED] writes:
I believe there's something similar for OS X as well. The question is:
would it be better to do that, or to just delay calling fsync until the
OS has had a chance to write things out.
A delay is not going to help unless you can suppress additional writes
Benny Amorsen wrote:
JCN == Jim C Nasby [EMAIL PROTECTED] writes:
JCN Truth is, I bet many (if not most) DBAs barely know that case
JCN matters in the units.
Sounds like the school system needs fixing, then.
Sure, but it probably shows a lot more prominently in other areas than
in unit
On Fri, 2006-12-29 at 16:41 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Fri, 2006-12-29 at 10:49 -0500, Tom Lane wrote:
Counterexample: table in which all tuples exceed half a page.
Current FSM code will ignore those too, if they are less than the
average size of the
Simon Riggs wrote:
On Fri, 2006-12-29 at 10:49 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I would suggest that we tracked whether a block has had 0, 1 or 1+
updates/deletes against it. When a block has 1+ it can then be
worthwhile to VACUUM it and to place it onto the
On Sat, 2006-12-30 at 09:22 +1100, Russell Smith wrote:
Simon Riggs wrote:
FSM code ignores any block with less space than 1 average tuple, which
is a pretty reasonable rule.
FSM serves a different purpose than DSM and therefore has an entirely
different set of rules governing what it
So I've got this patch (attached, against 8.2)
The goal is to track temp file usage as an aid to server tuning (such as
work_mem)
Most of the patch seems to work just dandy, except I'm getting weird
sizes reported:
2006-12-29 17:46:21 EST [45558]: [575-1] LOG: temp file: size 140737488343776
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
entirely.
4) GNUTLS development seems more active? OpenSSL has been in a
frozen/mature state for a while. I don't understand why OpenSSL is still
labelled as 0.9.x, which might indicate alpha quality, under heavy
development.
On Fri, 2006-12-29 at 17:57 -0500, Robert Treat wrote:
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
entirely.
4) GNUTLS development seems more active? OpenSSL has been in a
frozen/mature state for a while. I don't understand why OpenSSL is still
labelled as 0.9.x, which
On 12/29/06, Chris Browne [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Jaime Casanova) writes:
On 12/28/06, Tom Lane [EMAIL PROTECTED] wrote:
Galy Lee [EMAIL PROTECTED] writes:
So I am thinking another way to perform vacuum. For example vacuum can
be refined in a maintenance time frame like
On Fri, 2006-12-29 at 17:53 -0500, Bill Moran wrote:
So I've got this patch (attached, against 8.2)
The goal is to track temp file usage as an aid to server tuning (such as
work_mem)
Most of the patch seems to work just dandy, except I'm getting weird
sizes reported:
2006-12-29
Tom Lane wrote:
Richard Troy [EMAIL PROTECTED] writes:
... it occurs to me that perhaps Josh can implement
a command line switch to turn on command line numbering.
That would solve the problem I have with changing \s. I think a psql
\set variable (comparable to ON_ERROR_STOP and friends)
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
On Fri, 2006-12-29 at 17:57 -0500, Robert Treat wrote:
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
given options like --enable-dtrace and --with-libedit-preferred, I don't
find
this argument compelling...
I don't like either
On Fri, 2006-12-29 at 18:56 -0500, Stephen Frost wrote:
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
On Fri, 2006-12-29 at 17:57 -0500, Robert Treat wrote:
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
given options like --enable-dtrace and --with-libedit-preferred, I don't
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
I do not like --enable-dtrace because it is a Solaris only thing and a
waste of maintability resources (although small).
While the analysis can only be done on Solaris I feel that improvments
from the analysis may be useful on other platforms. For
I do not like --with-krb5 because it has extremely limited real world
use.
Riiigghhhttt... Only every Windows setup which uses Active Directory,
most major universities, and certain large corporations (uh, AOL?) would
even think to use something like Kerberos!
I said Extremely Limited
On Dec 29, 2006, at 7:09 PM, Joshua D. Drake wrote:
On Fri, 2006-12-29 at 18:56 -0500, Stephen Frost wrote:
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
On Fri, 2006-12-29 at 17:57 -0500, Robert Treat wrote:
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
given options like
I don't understand why this has devolved into an argument about what
people do and don't like. It's like specifically choosing a forum
that will have the most disagreement.
Yep :), I saw we go over to debian-general and ask why they are trying
to make all these projects use GNU/TLS ;)
* Joshua D. Drake ([EMAIL PROTECTED]) wrote:
I do not like --with-krb5 because it has extremely limited real world
use.
Riiigghhhttt... Only every Windows setup which uses Active Directory,
most major universities, and certain large corporations (uh, AOL?) would
even think to use
Alvaro Herrera wrote:
Tom Lane wrote:
Richard Troy [EMAIL PROTECTED] writes:
... it occurs to me that perhaps Josh can implement
a command line switch to turn on command line numbering.
That would solve the problem I have with changing \s. I think a psql
\set variable (comparable
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
I believe there's something similar for OS X as well. The question is:
would it be better to do that, or to just delay calling fsync until the
OS has had a chance to write things out.
A delay is not going to help unless you can
On Fri, 2006-12-29 at 20:59 -0500, Bruce Momjian wrote:
Alvaro Herrera wrote:
Tom Lane wrote:
Richard Troy [EMAIL PROTECTED] writes:
... it occurs to me that perhaps Josh can implement
a command line switch to turn on command line numbering.
That would solve the problem I have
On Fri, Dec 29, 2006 at 09:02:11PM -0500, Bruce Momjian wrote:
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
I believe there's something similar for OS X as well. The question is:
would it be better to do that, or to just delay calling fsync until the
OS has had a chance to
Robert Treat wrote:
On Friday 29 December 2006 14:49, Joshua D. Drake wrote:
entirely.
4) GNUTLS development seems more active? OpenSSL has been in a
frozen/mature state for a while. I don't understand why OpenSSL is still
labelled as 0.9.x, which might indicate alpha quality,
Bruce Momjian wrote:
Robert Treat wrote:
5) GNUTLS does not run well under all of our supported platforms.
given options like --enable-dtrace and --with-libedit-preferred, I don't
find
this argument compelling...
Keep in mind it took years to get OpenSSL support up to the level we
have
On Thu, Dec 21, 2006 at 11:43:27AM -0500, Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
You could make a case that we need *three* numbers: a permanent column
ID, a display position, and a storage position.
Could this not be handled by some catalog fixup after
On 12/29/06, Bruce Momjian [EMAIL PROTECTED] wrote:
No code yet, and I don't remember who said they were working on it.
I'm still waiting to hear from Mark Cave-Ayland on whether he's going
to pick it up or whether I'll just do it. One way or another, there
should be some movement regarding
Chris Browne [EMAIL PROTECTED] writes:
How you get the work to spread consistently across 6 hours is a
challenge; personally, my preference would generally be to try to get
the work done ASAP, so the goal seems a tad off to me...
I think the context for this is that you have an agreed-on
Bruce Momjian [EMAIL PROTECTED] writes:
Keep in mind it took years to get OpenSSL support up to the level we
have it now. It took SSL experts coming in and out of our development
process to get it 100% feature-complete.
Actually, it's *not* feature-complete even yet.
What basically bothers
79 matches
Mail list logo
