-- Weitergeleitete Nachricht --
Subject: Re: [BUGS] Endless loop in ExecNestLoop
Date: Dienstag, 31. Januar 2006 16:39
From: Tom Lane <[EMAIL PROTECTED]>
To: Philipp Reisner <[EMAIL PROTECTED]>
Cc: pgsql-bugs@postgresql.org
Philipp Reisner <[EMAIL PROTECTED]&
42092574) OR (ccu_objid = 42886947) OR (ccu_objid = 43813234))
-> Index Scan using devicetypes_pkey on devicetypes dty
(cost=0.00..3.04 rows=1 width=18)
Index Cond: (dty.objid = "outer".dty_objid)
-> Index Scan using bpartne
Am Montag, 30. Januar 2006 17:42 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > Version: 8.0.2
>
> I don't think so ... neither bitmap scans nor slot_getattr exist in 8.0.
>
Sorry, a typo, 8.1.2 of course.
> > Is this bug-report of any us
00537b4d in PostmasterMain ()
#32 0x000000536e59 in PostmasterMain ()
#33 0x004fda0c in main ()
With gdb's ability to execute until the current function (stack frame) return,
I found out which function (stack frame) is the up-most in this end
Am Dienstag, 19. August 2003 11:52 schrieb Philipp Reisner:
> Am Montag, 18. August 2003 15:38 schrieb Tom Lane:
> > Philipp Reisner <[EMAIL PROTECTED]> writes:
> > > Now if the applications issues one delete statement concurrently on
> > > two connections both
Am Montag, 18. August 2003 15:38 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > Now if the applications issues one delete statement concurrently on
> > two connections both block forever.
> >
> > Please correct me if I am wrong, but should not
ted EOF on
client connection
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austriahttp://www.linbit.com :
--
Am Donnerstag, 31. Juli 2003 15:53 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > Program received signal SIGSEGV, Segmentation fault.
> > DecodeDateTime (field=Cannot access memory at address 0x303038
> > ) at datetime.c:1404
> > 1404date
Am Mittwoch, 30. Juli 2003 16:00 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0812f9bc in DecodeDateTime ()
> > (gdb) where
> > #0 0x0812f9bc in DecodeDateTime ()
> > Can
Am Montag, 28. Juli 2003 15:53 schrieb Tom Lane:
> Philipp Reisner <[EMAIL PROTECTED]> writes:
> > If I execute this query several times (I receive the correct result set),
> > and then do an explain of the same query, the backend terminates with
> > sig 11 !!!
>
>
Am Montag, 28. Juli 2003 11:41 schrieb Peter Eisentraut:
> Philipp Reisner writes:
> > Once in a while (about 3 times a day) one or more INSERTS/DELETES simply
> > go into the "waiting" state, and block the whole database. The only way
> > out is to terminate the c
varying(1),
"location" character varying(50),
loc_objid integer,
tzo_objid integer,
pin character varying(50),
description character varying(4000),
department character varying(50),
sign character varying(50)
);
-Philipp
--
: Dipl-Ing Phili
stgres: sd sd [local] idle
16606 ?S 0:03 postgres: sd sd 10.2.1.5 idle in transaction
To get rid of the problem we tried to upgrade to 7.3.3. But see next
mail for our experiences with 7.3.3.
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
13 matches
Mail list logo
