| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Vilson farias" <vilson(dot)farias(at)digitro(dot)com(dot)br> |
| Cc: | pgsql-general(at)postgresql(dot)org, "EDUARDO TRIERWEILER Naschenweng" <eduardo(dot)naschenweng(at)digitro(dot)com(dot)br>, "SIMONE Carla MOSENA" <simone(dot)mosena(at)digitro(dot)com(dot)br> |
| Subject: | Re: Does pg_dump ignore indexes? |
| Date: | 2000-11-20 20:02:14 |
| Message-ID: | 2860.974750534@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Vilson farias" <vilson(dot)farias(at)digitro(dot)com(dot)br> writes:
> I've been testing hardly and now I found something interesting : these
> errors only happen when model/data are imported with pg_dump help, that is,
> all indexed fields are sequencially scanned when I do a select from some
> pk-indexed table, but if model/data where created/imported without pg_dump,
> then everything works fine. Does anyone know why this is happening?
Have you done a VACUUM ANALYZE after loading the pg_dump output?
It looks to me like the planner may not have statistics about the table...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2000-11-20 20:21:51 | Re: Cannot create users |
| Previous Message | Lamar Owen | 2000-11-20 19:57:41 | Re: Logging |