Re: [BUGS] Postgresql 7.3.2 Crash

2003-03-25 Thread Stephan Szabo
On Tue, 25 Mar 2003, Adrian Pop wrote: > I have a postgresql 7.3.2 crash. > Below you have the details. Okay, I think I've localized the cause (but not a fix). > name_id bigint not null default 0, I think the problem occurs with of the hack (mentioned in the last mail) b

[BUGS] Bug #920: The PostgreSql Server goes down

2003-03-25 Thread pgsql-bugs
Kallol Nandi ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description The PostgreSql Server goes down Long Description Hi, I am facing this problem when I start the PostgreSql database server and query any of the database.All the proce

Re: [BUGS] Backend crashe with signal 11 wher restoring big database.

2003-03-25 Thread KroK
Yes, RAM is ok. My server works with very high load and there are no problems at all... BTW, backend crashes both when used COPY and INSERT in the dump. I've split dump file into several parts and restore them one by one. Everything was ok. Krok. On Tue, Mar 25, 2003 at 12:35:34PM -0500, Dan La

Re: [BUGS] Bug report

2003-03-25 Thread Robert E. Bruccoleri
Dear Tom, > > > > If I gave you access to an SGI running PostgreSQL 7.3.2, would you > > be willing to log in and explore the problem "live"? > > You bet. Do you have gdb installed? Thank you so much. WRT to gdb, it's not available. However, you can use dbx, SGI's debugger. It's similar so yo

[BUGS] Bug #919: Can't initialize a database cluster in Cygwin/PostgreSQL 7.3.2

2003-03-25 Thread pgsql-bugs
Stephane Decleire ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Can't initialize a database cluster in Cygwin/PostgreSQL 7.3.2 Long Description Hi, When I try to initialize a new database cluster in Cygwin / PostgreSQL 7.3.2,

Re: [BUGS] Postgresql 7.3.2 Crash

2003-03-25 Thread Stephan Szabo
On Tue, 25 Mar 2003, Adrian Pop wrote: > I have a postgresql 7.3.2 crash. > Below you have the details. Hmm, I can reproduce this with current sources. Backtrace from core looks like a bug in the setdefault trigger (I'm at work so I don't have real access to source to get more details). > Now

[BUGS] Postgresql 7.3.2 Crash

2003-03-25 Thread Adrian Pop
Hello, I have a postgresql 7.3.2 crash. Below you have the details. All the files included here can be found at: http://www.ida.liu.se/~adrpo/postgresqlbug/ Operating systems (uname -a) 1: SunOS xxx.xxx.liu.se 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-5_10 2: Linux dostoievsky 2.4.18-27.8.0

Re: [BUGS] Bug #918: pg_dump problem w/ SEQUENCE

2003-03-25 Thread Laurent FAILLIE
Ok, I found what's append : 1/ current value of the sequence data are following : scheduling=# select * from seq_id_fch; sequence_name | last_value | increment_by | max_value | min_value | cache_value | log_cnt | is_cycled | is_called ---++--++---

Re: [BUGS] Backend crashe with signal 11 wher restoring big database.

2003-03-25 Thread Dan Langille
On 25 Mar 2003 at 18:13, KroK wrote: > Mar 25 15:14:08 frost postgres[338]: [14] LOG: server process (pid 64665) was > terminated by signal 11 > Mar 25 15:14:08 frost postgres[338]: [15] LOG: terminating any other active server > processes My understanding is that signal 11 normally indicates

[BUGS] Backend crashe with signal 11 wher restoring big database.

2003-03-25 Thread KroK
Your name : Krok Your email address : [EMAIL PROTECTED] System Configuration - Architecture : Dual PIII-500 Operating System : FreeBSD 4.7-RELEASE-p7 PostgreSQL version: PostgreSQL-7.3.2 Compiler used : gcc 2.

Re: [BUGS] Bug #918: pg_dump problem w/ SEQUENCE

2003-03-25 Thread Laurent FAILLIE
Hi Bruce, I duno where is the problem, because : 1/ if I do a simple CREATE SEQUENCE x; as you do, the output is ok, 2/ It works also if I do a CREATE SEQUENCE x START 1 INCREMENT 1 MAXVALUE 2147483647 MINVALUE 1 CACHE 1; which is the command used to recreate seq_id_fch wh

Re: [BUGS] Solution for bug #899

2003-03-25 Thread Bruce Momjian
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Laurent FAILLIE wrote: > Hello Bruce, >

Re: [BUGS] Bug #918: pg_dump problem w/ SEQUENCE

2003-03-25 Thread Bruce Momjian
I just did 'CREATE SEQUENCE x' and pg_dump produced: CREATE SEQUENCE x START WITH 1 INCREMENT BY 1 NO MAXVALUE NO MINVALUE CACHE 1; which has the proper value after START WITH. Any ideas why your setup is different? --

Re: [BUGS] Solution for bug #899

2003-03-25 Thread Laurent FAILLIE
Hello Bruce, there is a contextual diff of my patch w/ the current (I hope) snapshot of postgresql. I test it on my own database, but I found another bug w/ SEQUENCE this time. I have created a new ticket, #918 for this as it's totaly a separate problem. Bye Laurent -- *** pg_dump.c.org

[BUGS] Bug #918: pg_dump problem w/ SEQUENCE

2003-03-25 Thread pgsql-bugs
laurent faillie ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description pg_dump problem w/ SEQUENCE Long Description Hi all, in order to correct bug #899, I have downloaded the current snapshot and I discover a new trouble w/ pg_dump.