| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <hackers(at)postgreSQL(dot)org>, jamesh(at)interpath(dot)com, wieck(at)sapserv(dot)debis(dot)de |
| Subject: | Re: [HACKERS] VACUUM ANALYZE Problem |
| Date: | 1998-02-05 04:58:15 |
| Message-ID: | 34D946E7.7C1D36F4@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> OK, I have looked at this, but can't figure out how to fix the many
> initializations of ScanKeyData. Can someone who understands this please
> submit a patch for all these initializations so we can stop these vacuum
> analyze reports?
>
> Vadim has found the problem, but we need someone to properly fix it.
Just apply my patch to stop "analyze-problem" reports (sorry, I didn't it).
As for other (possible) places, note that ScanKeyEntryInitialize()
initializes sk_func.fn_oid and so we have to worry about hard-coded
initializations only (when ScanKeyEntryInitialize() is not called).
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Meskes, Michael | 1998-02-05 08:30:27 | RE: [HACKERS] Hi |
| Previous Message | Bruce Momjian | 1998-02-05 04:27:10 | Re: [HACKERS] VACUUM ANALYZE Problem |