Re: [QUESTIONS] Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering) - Mailing list pgsql-hackers

From Brett McCormick
Subject Re: [QUESTIONS] Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering)
Date
Msg-id 199801242246.OAA25123@abraxas.scene.com
Whole thread Raw
In response to Re: [QUESTIONS] Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering)  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Keep in mind that the entire database gets locked for as long as
you've got it open in read/write mode, regardless of if you've read or
written.

On Fri, 23 January 1998, at 22:53:27, Bruce Momjian wrote:

> >     You'd be better off looking at something like GDBM (which, by the
> > way, also creates a lock against updates while another is reading the
> > database)...unless I'm missing something, you aren't looking at doing
> > anything that *requires* an SQL engine :(
>
> I agree.  GDBM is a fine system for such uses.

pgsql-hackers by date:

Previous
From: Goran Thyni
Date:
Subject: Re: [HACKERS] fork/exec for backend
Next
From: Brett McCormick
Date:
Subject: Re: [HACKERS] Re: Browsing the tables and why pgsql does not perform well