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

From The Hermit Hacker
Subject Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering)
Date
Msg-id Pine.BSF.3.96.980124003112.28536m-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] Show stopper ? (was: Re: "cruising" or "browsing" through tables using an index / ordering)  (Jan Vicherek <honza@ied.com>)
List pgsql-hackers
On Fri, 23 Jan 1998, Jan Vicherek wrote:

> > You can put an index on the table, and embed a function inside the
> > engine to spin through the index, getting valid rows.
>
>   Aha, this implies that in the index there are valid and non-valid rows.
> I guess those that are to be "valid" (no current transactions on that
> row) and the non-valid "those that are subject to an update lock /
> transaction".

    There is no record level locking available at this point in time,
only table level.  Bruce, just curious...this whole discussion...would it
be moot if we did have record level locking?

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: Attn PG gurus / coders : New approach for ORDER BY ? (was: Re: Show stopper ?)
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Re: Attn PG gurus / coders : New approach for ORDER BY ?