| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: ANALYZE patch for review |
| Date: | 2004-02-13 14:41:22 |
| Message-ID: | 2010.1076683282@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> writes:
> The only reason I kept the Relation parameter
> was because I wasn't sure if there was a historical reason why someone
> would need the relation information as well as the attribute
> information.
I can't think of one, but if someone did, they could extract the
relation OID from the pg_attribute row and re-open it for themselves.
So AFAICS this API does not omit any critical info.
I forgot to email you about the fetch_function revision, but I trust
it meets with your approval. Right now it's just a wrapper around
heap_fetch, but I thought we might conceivably want something different
when we do functional-index stats. The fetch function will give us
wiggle room if we need it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick Barr | 2004-02-13 15:55:45 | TODO : Multiple inserts in a single statement |
| Previous Message | Bruce Momjian | 2004-02-13 14:22:51 | Re: temp patch for win32 readdir issue |