| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | P3 Consulting <p3c(at)p3-consulting(dot)net>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: BUG: pgIndex.cpp |
| Date: | 2005-01-12 09:27:16 |
| Message-ID: | 41E4ED74.3060409@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Dave Page wrote:
> Did you get a chance to look at this? It seems to me that the quick and
> dirty solution is to wrap the index->iSetxxx calls in an 'if (index)',
> however I'm not entirely convinced that is safe given that it's possible
> to return a null index pointer to the caller (which without significant
> trawling through code I may not find all instances of).
I don't see the point catching this beyond an assert. A sane pgsql will
never return contype != p, u, or NULL unless system tables are corrupted.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-01-12 09:33:12 | Re: BUG: pgIndex.cpp |
| Previous Message | Dave Page | 2005-01-12 09:12:40 | Re: BUG: pgIndex.cpp |