Patrick Welche wrote:
On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
He was testing 7.4devel. That's not the right one.
What's the difference? (Do I really want to wait another day while this
ancient box compiles it given that the chances of it working under
7.4devel
May be I miss something, but seems there is a problem with float4
in 7.2.3 and 7.3RC1 (6.53 works fine):
test=# create table t ( a float4);
CREATE TABLE
test=# insert into t values (0.1);
INSERT 32789 1
test=# select * from t where a=0.1;
a
---
(0 rows)
test=# select * from t where
Bruce Momjian [EMAIL PROTECTED] wrote:
Tom, can you clarify why -0 is valid. Is it for _small_ near zero
values that are indeed negative?
Branch Cuts for Complex Elementary Functions, or Much Ado About
Nothing's Sign Bit W. Kahan; ch. 7 in _The State of the Art in
Numerical Analysis_ ed.
Oleg Bartunov [EMAIL PROTECTED] writes:
May be I miss something, but seems there is a problem with float4
in 7.2.3 and 7.3RC1 (6.53 works fine):
test=# create table t ( a float4);
CREATE TABLE
test=# insert into t values (0.1);
INSERT 32789 1
test=# select * from t where a=0.1;
a
---
Tom Lane writes:
AFAIK, all modern hardware claims compliance to the IEEE floating-point
arithmetic standard, so failure to print minus zero as minus zero is
very likely to be a software issue not hardware. That suggests strongly
that the issue is netbsd version (specifically libc version)
Heres a patch which will create the sql_help.h file if it doesn't already
exist using an installed copy of perl. I've tested it using perl v5.6.1 from
ActiveState and all appears to work.
Can someone commit this for me, or throw back some comments.
Thanks,
Al.
--- src/bin/psql/win32.mak
Doug McNaught [EMAIL PROTECTED] writes:
Oleg Bartunov [EMAIL PROTECTED] writes:
May be I miss something, but seems there is a problem with float4
in 7.2.3 and 7.3RC1 (6.53 works fine):
test=# create table t ( a float4);
CREATE TABLE
test=# insert into t values (0.1);
INSERT 32789 1
On Wed, Nov 20, 2002 at 06:48:15PM +0100, Peter Eisentraut wrote:
Tom Lane writes:
AFAIK, all modern hardware claims compliance to the IEEE floating-point
arithmetic standard, so failure to print minus zero as minus zero is
very likely to be a software issue not hardware. That suggests
Patrick Welche [EMAIL PROTECTED] writes:
Right, the equivalent for NetBSD vfprintf.c is:
revision 1.40
date: 2001/11/28 11:58:22; author: kleink; state: Exp; lines: +4 -4
Since we're returned the sign of a floating-point number by __dtoa(),
use that to decide whether to include a minus
Peter Eisentraut [EMAIL PROTECTED] writes:
The next FreeBSD subrelease (4.8?) should have this fixed. OpenBSD is not
fixed. NetBSD and Darwin seem to have temporarily hidden their cvsweb in
shame, but I would assume it's the same issue. Not sure what HP-UX is
doing about it.
HP has
On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
Patrick Welche [EMAIL PROTECTED] writes:
...
NetBSD 1.5 has revision 1.32, NetBSD 1.6 has revision 1.42
Ah-hah, so it is a version issue --- we could make the resultmap line
something like
Patrick Welche [EMAIL PROTECTED] writes:
On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
Ah-hah, so it is a version issue --- we could make the resultmap line
something like
geometry/.*-netbsd1.[0-5]=geometry-positive-zeros
NetBSD/i386-1.6H i386-unknown-netbsdelf1.6H
On Wed, Nov 20, 2002 at 01:51:28PM -0500, Tom Lane wrote:
Patrick Welche [EMAIL PROTECTED] writes:
On Wed, Nov 20, 2002 at 01:21:47PM -0500, Tom Lane wrote:
Ah-hah, so it is a version issue --- we could make the resultmap line
something like
Patrick Welche [EMAIL PROTECTED] writes:
Just realised: the answers I gave above were with the config.guess from
automake 1.7a!
% uname -srmp
NetBSD 1.6K acorn32 arm
% postgresql-7.3rc1/config/config.guess
acorn32-unknown-netbsd1.6K
% automake/lib/config.guess
On Wed, Nov 20, 2002 at 09:33:41AM -0500, Bruce Momjian wrote:
Patrick Welche wrote:
On Tue, Nov 19, 2002 at 06:22:08PM +0100, Peter Eisentraut wrote:
He was testing 7.4devel. That's not the right one.
What's the difference? (Do I really want to wait another day while this
ancient
Ports list updated:
http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
---
Patrick Welche wrote:
On Wed, Nov 20, 2002 at 09:33:41AM -0500, Bruce Momjian wrote:
Patrick Welche wrote:
On Tue,
On Wed, 2002-11-20 at 21:35, Robert Treat wrote:
On Wed, 2002-11-20 at 03:53, Oliver Elphick wrote:
On Mon, 2002-11-18 at 15:45, Thomas Aichinger wrote:
Hi,
I recently installed pg 7.2.3 on my linux box and discovered that
there are some problems with datatype serial and sequence.
This requires changing the nextval() function to be an attribute of the
sequence.
ie. sequence.nextval and sequence.currval to deal with the sequence.
It should also be on the todo list.
On Wed, 2002-11-20 at 17:12, Oliver Elphick wrote:
On Wed, 2002-11-20 at 21:35, Robert Treat wrote:
On
Tom Lane wrote:
Log message:
Finish implementation of hashed aggregation. Add enable_hashagg GUC
parameter to allow it to be forced off for comparison purposes.
Add ORDER BY clauses to a bunch of regression test queries that will
otherwise produce randomly-ordered
Oliver Elphick wrote:
On Wed, 2002-11-20 at 21:35, Robert Treat wrote:
On Wed, 2002-11-20 at 03:53, Oliver Elphick wrote:
On Mon, 2002-11-18 at 15:45, Thomas Aichinger wrote:
Hi,
I recently installed pg 7.2.3 on my linux box and discovered that
there are some problems with
Bruce Momjian [EMAIL PROTECTED] writes:
Tom, do we really want to add a GUC that is used just for comparison of
performance? I know we have the seqscan on/off, but there are valid
reasons to do that. Do you think there will be cases where it will
faster to have this hash setting off?
Sure
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom, do we really want to add a GUC that is used just for comparison of
performance? I know we have the seqscan on/off, but there are valid
reasons to do that. Do you think there will be cases where it will
faster to have this hash
The documentation on changing shared memory kernel settings on xBSD
(namely FreeBSD, possibly others as well) isn't ideal, IMHO. It says:
%%
The options SYSVSHM and SYSVSEM need to be enabled when the
kernel is compiled. (They are by default.) The maximum size of
shared memory is
On 20 Nov 2002, Neil Conway wrote:
However, the FreeBSD box I'm playing with isn't mine, so I'm not too
keen to change sysctls (well, that and I don't have root :-) ). Would
a kind BSD user confirm that:
(a) the sysctls above *can* be used to change kernel shared
memory
Justin Clift [EMAIL PROTECTED] writes:
This sounds like a serious bug in our behaviour, and not something
we'd like to release.
It's not ideal, I agree, but I *definately* don't think this is
grounds for changing the release schedule.
No real issue with the nicety for newbies, but am very
Neil Conway wrote:
Justin Clift [EMAIL PROTECTED] writes:
This sounds like a serious bug in our behaviour, and not something
we'd like to release.
It's not ideal, I agree, but I *definately* don't think this is
grounds for changing the release schedule.
Hey, I'm no fan of slowing the
Justin Clift [EMAIL PROTECTED] writes:
Oliver Elphick wrote:
I created a sequence using SERIAL when I created a table. I used the
same sequence for another table by setting a column default to
nextval(sequence).
I deleted the first table. The sequence was deleted too, leaving the
default
Apparently only some settings are adjustable.
root@dev:~# uname -smr
FreeBSD 4.2-RELEASE i386
root@dev:~# sysctl -a | grep kern.ipc.semm
kern.ipc.semmap: 30
kern.ipc.semmni: 10
kern.ipc.semmns: 60
kern.ipc.semmnu: 30
kern.ipc.semmsl: 60
root@dev:~# sysctl -w kern.ipc.semmap=50
kern.ipc.semmap:
28 matches
Mail list logo
