| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pinker <pinker(at)onet(dot)eu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Mistake in documentation? ANALYZE on partitioned tables |
| Date: | 2014-12-03 16:42:03 |
| Message-ID: | 17796.1417624923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
pinker <pinker(at)onet(dot)eu> writes:
> As I have read in documentation
> <http://www.postgresql.org/docs/9.3/static/ddl-partitioning.html> that "If
> you are using manual VACUUM or ANALYZE commands, don't forget that you need
> to run them on each partition individually. A command like: ANALYZE
> measurement; will only process the master table."
> But when I run ANALYZE VERBOSE orders; (test table with 12 partitions) I
> get:
> All partitions were processed...
> So I guess: mistake in documentation?
No. All the partitions were *scanned*, to generate whole-inheritance-tree
statistics for the parent table. But this did not update stats associated
with the individual child tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mongoose | 2014-12-03 18:08:24 | Re: Merge rows based on Levenshtein distance |
| Previous Message | Tim Schäfer | 2014-12-03 16:25:41 | Re: Auto vacuum not running -- Could not bind socket for statistics collector |