Skip site navigation (1) Skip section navigation (2)

Re: The Data Base System is in recovery mode

From: Palle Girgensohn <girgen(at)partitur(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: The Data Base System is in recovery mode
Date: 2000-10-18 16:19:28
Message-ID: 8766mqktpr.fsf@palle.girgensohn.se (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Palle Girgensohn <girgen(at)partitur(dot)se> writes:
> > New facts: The problem "moved" when raising the -B from default (64)
> > to 1000 (-N 100 now). Now, here's what happens:
> 
> Interesting.

I am also using -o -S 2048 now, but I doubt it helps...

> > query: CREATE VIEW wtabmaria AS SELECT  p.personid,p.foretag,p.fnamn,p.enamn,p.titel,p.telefon,p.mobil,p.email,p.tidpunkt FROM personer p WHERE true AND low
> > er(p.enamn)~~lower('Branner%')
> 
> Hm, you had not mentioned before that wtabmaria is a view.  That may be
> the critical factor.  However, I'm still not having any luck duplicating
> the failure.

Oh, gee. sorry! I slipped with the mouse when cut'n'pasting. The first
statement should be a create view. The view is dropped and created
"on-the-fly" with different where-clauses every time, depending on the
user's search arguments. As I might have said before, I am not the
programmer... I think I would have the view created once, and done
"select from view where..." Maybe that would help, but there is still
a bug in postgres, I guess?

> > It looks very much like an out-of-memory error,

I must take that back, since the select from view only holds two
records... My mistake, again...

> I don't think I believe that; out-of-memory problems should be reported
> as such.  Moreover, I see nothing in this query that would require
> touching more than one disk buffer at a time.  Now I really want to see
> the coredump backtrace...
> 
> > There are about 5500 records in this table.
> 
> Is that total in "personer", or total shown by the view?

in "personer".

Also, I have suddenly become a "very lousy bug reporter", sorry. I forgot the indices:

CREATE  INDEX "personer_fnamn_idx" on "personer" using btree ( lower ("fnamn") "text_ops" );
CREATE UNIQUE INDEX "personer_personid_index" on "personer" using btree ( "personid" "int4_ops" );
CREATE  INDEX "personer_personid_fname_idx" on "personer" using btree ( "personid" "int4_ops", "fnamn" "text_ops" );

Cheers,
Palle

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2000-10-18 16:51:58
Subject: Re: The Data Base System is in recovery mode
Previous:From: Bruce MomjianDate: 2000-10-18 16:19:14
Subject: Re: Re: 7.0.3 to_char() (was: [BUGS] Bugs in to_char function)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group