| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hannes Dorbath <light(at)theendofthetunnel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Index trouble with 8.3b4 |
| Date: | 2008-01-14 21:29:18 |
| Message-ID: | 1200346158.10057.438.camel@dogma.ljc.laika.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sun, 2008-01-13 at 18:52 -0500, Tom Lane wrote:
> The scan is done using the regular heapscan code, which in 8.3 has been
> modified to enable "synchronized scanning", which means it might start
> from the middle of the table and wrap around. If that happens, the
> "merge join" will get totally confused because it is expecting the
Thank you and Hannes Dorbath for tracking this down.
> I wonder whether there are any other places that are silently assuming
> that heapscans start from page zero ...
>
I considered that question when implementing sync scans, but I could not
think of any specific areas of the code that would likely be affected.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Rich | 2008-01-14 21:31:00 | Re: Locking & concurrency - best practices |
| Previous Message | Scott Marlowe | 2008-01-14 21:15:00 | Re: Locking & concurrency - best practices |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2008-01-14 21:32:08 | Re: to_char incompatibility |
| Previous Message | Magnus Hagander | 2008-01-14 21:20:14 | Re: Re: [COMMITTERS] pgsql: Most recent Postgres version is 8.2.6, per report from Robert |