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

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

From: Brett McCormick <brett(at)abraxas(dot)scene(dot)com>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: scrappy(at)hub(dot)org, honza(at)ied(dot)com, dustin(at)spy(dot)net, pgsql-questions(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [QUESTIONS] Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering)
Date: 1998-01-24 22:46:58
Message-ID: 199801242246.OAA25123@abraxas.scene.com (view raw or flat)
Thread:
Lists: 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.

In response to

pgsql-hackers by date

Next:From: TomDate: 1998-01-24 22:53:22
Subject: Re: [HACKERS] fork/exec for backend
Previous:From: Goran ThyniDate: 1998-01-24 22:16:53
Subject: Re: [HACKERS] fork/exec for backend

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