| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | mac_man2005(at)hotmail(dot)it |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Backward reading |
| Date: | 2008-02-01 20:35:22 |
| Message-ID: | 1201898122.4252.88.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2008-02-01 at 19:25 +0100, mac_man2005(at)hotmail(dot)it wrote:
> PostgreSQL allows "backward reading" tuples writing the tuple's length
> after and before the tuple proper, in case a 'randomAccess' is
> requested.
>
> Is there any example of backward reading tuples into PostgreSQL code?
Don't think so, but we don't always use randomAccess anyway. Sounds like
we might be able to drop the length at the end of each tuple in those
cases...
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-01 21:25:01 | Re: BUG #3921: CREATE TABLE / INCLUDING INDEXES fails with permission denied |
| Previous Message | mac_man2005 | 2008-02-01 18:25:08 | Backward reading |