| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.3.4 vacuum/analyze error |
| Date: | 2004-09-30 02:59:14 |
| Message-ID: | 8854.1096513154@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
>> Either increase your per-process memory limit, or reduce the statistics
>> targets for this table ...
> What am I missing?
> $ ulimit -a
> time(seconds) unlimited
> file(blocks) unlimited
> data(kbytes) 131072
^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is where the limit is coming from ...
> $ psql -c "select name, setting from pg_settings" | egrep stats_
> stats_block_level | off
Those are not the statistics I'm talking about. I was assuming that
you'd done ALTER TABLE SET STATISTICS somewhere along the line, or
changed default_statistics_target. If you haven't, then this must
be a pretty strange table --- how many columns has it got?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2004-09-30 03:18:24 | Re: 7.3.4 vacuum/analyze error |
| Previous Message | Ed L. | 2004-09-30 02:52:57 | Re: 7.3.4 vacuum/analyze error |