Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev)
Cc: alvin(at)camberlo(dot)demon(dot)co(dot)uk, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)
Date: 1998-02-26 14:44:34
Message-ID: 199802261444.JAA14219@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> BTW, elog(FATAL) from vacuum and btree were reported by 2-3
> another ppl - shouldn't we ask users to re-compile server with
> CASSERT in all "FATAL" cases ?
> CASSERT assisted me very much to find real sources of this problem
> and recently fixed vacuum bug.

I am a little confused on when we should have them use this. In most
cases, turning on CASSERT doesn't help. Should we suggest it in certain
cases as we see it applies, or is there a rule we can give them to tell
them when to try it?

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Martin 1998-02-26 15:46:37 Snapshot 26Feb98 - configure still broken
Previous Message Maurice Gittens 1998-02-26 14:42:42 Re: [HACKERS] Adding a field to each tuple