I compiled on Linux with no extra options.
using the psql monitor comman line editing works but psql will abort
with signal 11 (SIGSEV) when trying to do a real edit by using \e
--
mfG
* Hans-Ulrich SchaeferPhone: +(0)89-289-27819 *
* LRZ Abt. Hochleistungsrechnen
On Fri, Aug 13, 2004 at 02:41:26PM +0200, Hans-Ulrich Schaefer wrote:
I compiled on Linux with no extra options.
using the psql monitor comman line editing works but psql will abort
with signal 11 (SIGSEV) when trying to do a real edit by using \e
Confirmed on Solaris 9.
test= \e
Confirmed on BSD/OS. Looks like we found us a bug.
---
Michael Fuhr wrote:
On Fri, Aug 13, 2004 at 02:41:26PM +0200, Hans-Ulrich Schaefer wrote:
I compiled on Linux with no extra options.
using the psql monitor
Hans-Ulrich Schaefer [EMAIL PROTECTED] writes:
using the psql monitor comman line editing works but psql will abort
with signal 11 (SIGSEV) when trying to do a real edit by using \e
Fixed --- thanks for the report!
regards, tom lane
---(end of
This look like it would be nice to have it configurable.
first_day_of_the_week
first_day_of the_year
Tom Lane wrote:
PostgreSQL Bugs List [EMAIL PROTECTED] writes:
Frankly speaking I don`t know the adequate calendar ISO norm in detail, but
the last days of year shouldn`t be counted as F_I_R_S_T
Tom Lane wrote:
So forget my previous proposed patch and try this one:
/* skip leading whitespace */
while (*num != '\0' isspace((unsigned char) *num))
num++;
errno = 0;
val = strtod(num, endptr);
+ if (endptr != num endptr[-1] == 0)
+
Hello!
I downloaded and installed PostgreSQL 8.0-beta1.
After I successfully started the server, any client
connection fails to the server with the follwing
in the log file
LOG: database system was shut down at 2004-08-11 14:05:49 Central
Europe Daylight Time
hello all,
this is the output as asked by Tom Lane.
test8= \set VERBOSITY verbose
test8= SELECT 'infinity'::float4;
float4
--
Infinity
(1 row)
test8= SELECT 'infinity'::float4;
ERROR: 22P02: invalid input syntax for type real: infinity
LOCATION: float4in, float.c:330
Following
I googled a bit and it seems that this error is caused by global
variables that are either not initialized or not declared extern.
gcc -no-cpp-precomp -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -D_REENTRANT -D_THREAD_SAFE
-D_POSIX_PTHREAD_SEMANTICS -I.
dbsize.c was not updated to use the new tablespace-aware function.
I am not well versed enough with the new function to know if GLOBAL...
was the correct default for what dbsize is trying to do. I just thought
you guys might want to know.
Thanks for the WORLD'S GREATEST OpenSource DB!
--
Hi folks,
hope this address is for successfull compilations to.
Today, I compiled 8.0 Beta on my NetBSD machine (single-CPU AMD Athlon):
[EMAIL PROTECTED] {3} uname -mrs
NetBSD 2.0G i386
[EMAIL PROTECTED] {4} /usr/local/pgsql/bin/postgres -V
postgres (PostgreSQL) 8.0.0beta1
I have a typescript of
That fixed it, it works now as I had hoped. Thanks again
From: Tom Lane [EMAIL PROTECTED]
To: Bob Henkel [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: [BUGS] BUG #1215: Call sql function from plpgsql results vary.
Date: Wed, 11 Aug 2004 23:06:09 -0400
PostgreSQL Bugs List [EMAIL
Hi,
I created a new database in the win32
version of 8.0 beta1 and added some functions.
I then did a pg_dump like so:
C:\Program Files\PostgreSQL\8.0-beta1\binpg_dump
--username=postgres --format=c
--file=c:\testdb.bak testdb
the backup is created successfully.
I then try to restore with
Did you set your client encoding? If not, you are probably inserting
WIN 1250-encoded characters without the system knowing about it. If
that happens, the ordering can be incorrect.
Yes, I set client encoding to WIN1250 and the ordering is incorect. I try set server
encoding to
Your name : A Wu
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) : AMD Opteron 242
Operating System (example: Linux 2.4.18) : Linux 2.6.7-gentoo-r13 x86_64
PostgreSQL version (example:
Hello,
I downloaded the 8.0 beta Windows installer at http://pgfoundry.org/projects/pginstaller.
It installed wihtout any issue on my W2K SP4
machine.
However, when trying to install it on a W2K server
through a terminal server session, I havethe
followingerror:
initdb.log
Bruce Momjian wrote:
OK, I have some more information. Basically, the config/acx_pthread.m4
manual page (http://www.gnu.org/software/ac-archive/htmldoc/acx_pthread.h=
tml)
says:
=09
NOTE: You are assumed to not only compile your program with these flags,
but also link it with them
When pg_ctl fails to start postmaster, an event should be logged
containing the reason. This information is available on the command
line, so it should be possible to use the Windows event log.
Here is what I did:
I installed PostgreSQL 8.0 beta 1 on Windows XP Pro, using the installer
from
Version: "PostgreSQL 8.0.0beta1 on i686-pc-mingw32,
compiled by GCC gcc.exe (GCC) 3.2.3 (mingw special 20030504-1)"
Tool: pgAdminIII
Error: create new database in pgAdmin, select
encoding as WIN1250, after ok there is message "ERROR: WIN1250 is not valid
encoding name"
Hi,
PostgreSQL version:
---
8.0-beta1 (windows)installed as a service.
Server Platform:
Windows XP professional SP1
Intel 2,4 Ghz/512 Mb
General test situation:
A
I have a very strange bug with postgres 7.4.3. I have a table with about
15 million rows and recently, duplicate rows have started appearing.
For simplicity, let's say my table is as follows:
files
---
fileid integer -- Primary key generated by a sequence
userid integer -- id of
I tried to build postgresql-8.0.0beta1 on an OpenBSD 3.5 (i386) system and it
failed. The configure script ran fine with no errors, but when I typed make
it complained that I needed gmake. So I installed gmake and it's
dependencies. So I run gmake and get this error (see attached file,
Hi,
if I choose in new version 8.0 for win32 czech locales then lc-collate is
czech_czech republic.1250. So I suppose that strings are compared by WIN1250 charset,
but database encoding can't be set as WIN1250 (only ISO8859-2=LATIN2) and then ORDER
BY don't work correctly. I
I am running the Win32 build installed of the msi installer on a Win2K box.
After installing the database, I created a new database named 'FPMain' and a
new table named 'Trusted' with one column also named 'Trusted' of
varchar[100] NOT NULL. When I went to edit the table, the column showed up,
I'm having issues installing PostgreSQL 8.0 Beta Build 20040809 on
Windows XP Home with SP2.
I'm having two different problems. First problem is when it comes time
to initialize the database with initdb. This fails and I get Failed
to create process for initdb: 1058! as an error message. My next
On Tue, Aug 10, 2004 at 12:17:47PM +0200, [EMAIL PROTECTED] wrote:
attached are the regression.out and regression.diffs files from make check on a
Ultra 2 dual 300MHz CPU running Solaris 9 OS.
Looks like no errorbut the expected due to difference in fp results.
[snip]
SELECT
The install is a generic fedora core 1 install with few mods,
notably bison upgraded to bison-1.875-5; the CPU is a
P4 3.06GHz from last year.
here's /proc/cpuinfo
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R)
Hi,
Saw the new Beta of PostgreSQL had a Windows installer, so I took a stab at
it.
My machine is running Windows XP on a Dell 2GHz 512MB RAM laptop.
I ran the postgresql-8.0-beta1-20040809.msi installer.
I went with the defaults for what to install.
I told the installer to create the
Greetings,
Gettings the following on my HPUX workstation:
== removing existing temp installation==
== creating temporary installation==
== initializing database system ==
== starting
On 10/8/04 10:19 pm, Tom Lane [EMAIL PROTECTED] wrote:
Theodore Petrosky [EMAIL PROTECTED] writes:
this is the error I get with 'make check'.
dyld:
/Users/postgres/software/postgresql-8.0.0beta1/src/test/regress/./tmp_check/i
nstall//usr/local/pgsql/bin/initdb
can't open library:
Tom Lane wrote:
This seems quite bizarre: ' -INFINiTY ' works but
'infinity' does not? Please try in psql
\set VERBOSITY verbose
SELECT 'infinity'::float4;
and send along the output.
It's even a little more bizarre:
When I start a fresh psql session, SELECT
pg_dump/restore in 8.0beta1 are not working well with formats other
thans plain text:
$ pg_restore --version
pg_restore (PostgreSQL) 8.0.0beta1
$ pg_dump --version
pg_dump (PostgreSQL) 8.0.0beta1
$ createdb test_8
CREATE DATABASE
$ createlang plpgsql test_8
$ psql test_8 -c \
create function
Hello!
Bruce Momjian wrote:
Robert Treat wrote:
`pthread_once'
../../../src/interfaces/libpq/libpq.so: undefined reference to
`pthread_key_create'
../../../src/interfaces/libpq/libpq.so: undefined reference to
`pthread_setspecific'
collect2: ld returned 1 exit status
Please describe a way to
I'm not sure I understand you, but you are saying that it is not working for
you, right? Try setting it to
export env
DYLD_LIBRARY_PATH=/Users/postgres/software/postgresql-8.0.0beta1/src/test/re
gress/tmp_check/install/usr/local/pgsql/lib/
adam
I hope we are okay with this... I tried your
Hi,
I am trying to compile Postgres-8.0.0beta1 on Solaris 8/x86, using Sun's
C compiler, and get the following error which told me to contact you :-
../../../../src/include/storage/s_lock.h, line 654: #error: PostgreSQL
does not have native spinlock support on this platform. To continue the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
INSTALLATION REPORT:
postgres runs fine on Linux (i386, sid, 2.4.27) I checked
basic functionality and multibyte encodings.
TYPOS:
* postgresql.conf says that you may specify interfaces in
listen_addresses, it should read hostnames.
NITPICKING:
Greetings,
The problem was solved by doing a make install followed by make check
Regards,
Verbus
916-765-1624 Cell
From: Verbus M. Counts [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [BUGS] regression test failure on 8.0.0beta1
Date: Tue, 10 Aug 2004 12:14:53 -0700
Nathan Daniels wrote:
I am running the Win32 build installed of the msi installer on a Win2K box.
After installing the database, I created a new database named 'FPMain' and a
new table named 'Trusted' with one column also named 'Trusted' of
varchar[100] NOT NULL. When I went to edit the table,
Andras Kutrovics wrote:
LOG: select() failed in statistics collector: An operation was
attempted on something that is not a socket.
What's your operating system platform?
Regards,
Andreas
---(end of broadcast)---
TIP 7: don't forget to increase
Holger Klawitter [EMAIL PROTECTED] writes:
TYPOS:
* postgresql.conf says that you may specify interfaces in
listen_addresses, it should read hostnames.
I think it means what it says. Interfaces are what you can actually
bind to or not bind to, at least with the TCP stacks I've worked with.
Mark Round [EMAIL PROTECTED] writes:
I am trying to compile Postgres-8.0.0beta1 on Solaris 8/x86, using Sun's
C compiler, and get the following error which told me to contact you :-
../../../../src/include/storage/s_lock.h, line 654: #error: PostgreSQL
does not have native spinlock support
Verbus M. Counts [EMAIL PROTECTED] writes:
The problem was solved by doing a make install followed by make check
Yes, on HPUX I think you probably have to do this. We build the
executables with SHLIB_PATH disabled, so even if pg_regress knew to
set SHLIB_PATH (which it does not) the programs
Andrew M. Campbell [EMAIL PROTECTED] writes:
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations
-DFRONTEND -I../../../src/interfaces/libpq -I../../../src/include -c -o initdb.o
initdb.c
initdb.c: In function `get_encoding_from_locale':
initdb.c:744: `CODESET'
Zeki Mokhtarzada [EMAIL PROTECTED] writes:
Notice that 3787433 is duplicated. How could this have happened if that
column is flagged as the primary key. Even more interesting:
select oid, fileid, userid from files where userid = 1898598 order by
fileid;
oid| fileid | userid
Edmund Bacon [EMAIL PROTECTED] writes:
pg_dump/restore in 8.0beta1 are not working well with formats other
thans plain text:
What seems to be broken is --clean mode, because it drops and fails to
restore the public schema. I can see no reason that it wouldn't
work exactly the same regardless
J. Hondius [EMAIL PROTECTED] writes:
These statements:
insert into tbverantwoording (dnkeyaanstelling, dnjaarweek,
dnkeyactiviteitenschema) values (27, 200343, 1781); insert into
tbverantwoording (dnkeyaanstelling, dnjaarweek,
dnkeyactiviteitenschema) values (27, 200343, 1780);
Reported
Zeki Mokhtarzada [EMAIL PROTECTED] writes:
The system is running on a Dell PowerEdge 2650 running RedHat 8. We had a
kernel halt about two weeks ago that was caused by one of our disk mirrors
failing. It could be that these problems were caused at that point in
time and are just being
Zeki Mokhtarzada [EMAIL PROTECTED] writes:
It appears that I can select the rows, but not delete or update them.
That's *very* odd, because it works for me. Is the same true of both
those duplicate rows, or did you only try the one with nonzero xmax?
I think there must be something we don't
48 matches
Mail list logo
