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 19:34:42 |
Message-ID: | 87y9zmj63x.fsf@palle.girgensohn.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Palle Girgensohn <girgen(at)partitur(dot)se> writes:
> 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?
>
> I agree, that is a bizarre way to do things, not least because it
> wouldn't work for multiple concurrent clients (unless the view name
> is client-specific?).
They *are* client specific. wtabmaria is "Maria's working table", sort
of...
> But I don't see why it would provoke a crash.
> Curiouser and curiouser.
>
> The indexes are good to know about, but AFAICT they won't be used
> for these particular queries. So I'm still unable to duplicate the
> problem. Looking forward to that backtrace...
I'll get on with it this weekend.
Cheers,
Palle
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2000-10-19 05:30:59 | Re: Re: 7.0.3 to_char() (was: [BUGS] Bugs in to_char function) |
Previous Message | Bruce Momjian | 2000-10-18 16:57:10 | Re: Re: 7.0.3 to_char() (was: [BUGS] Bugs in to_char function) |