From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Haase <haaseg(at)onefreevoice(dot)com> |
Cc: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: json datatype and table bloat? |
Date: | 2013-11-01 18:50:27 |
Message-ID: | 18449.1383331827@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gregory Haase <haaseg(at)onefreevoice(dot)com> writes:
> The json_data column is not accounted for in pg_stats:
Ah! I hadn't twigged to the fact that your bloat measurement approach
assumed you had pg_stats entries for all the columns.
> So I'm not sure if I'd actually qualify this as a "bug", but it appears
> that there is no way to currently get stats on a json data type.
ANALYZE currently punts on columns that don't have an equality operator,
which json does not. There isn't that much in the way of stats that we
could collect, though I suppose we could still compute average datum width
and null fraction.
I'm not sure whether there are plans to invent an equality operator for
json.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Janek Sendrowski | 2013-11-01 19:06:55 | Searching for appropriate pivots for my Fixed Query Array |
Previous Message | Gregory Haase | 2013-11-01 18:18:38 | Re: json datatype and table bloat? |