| From: | David Johnston <polobo(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: json datatype and table bloat? |
| Date: | 2013-11-04 18:14:51 |
| Message-ID: | 1383588891184-5776880.post@n5.nabble.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
ajelinek(at)gmail(dot)com wrote
> Along the lines of the equality operator; I have ran into issues trying to
> pivot a table/result set with a json type due what seemed to be no
> equality
> operator.
For the curious, and also use-case considerations for development, would you
be able to share what it is you are doing (and how) that combines full json
documents with pivoting?
Compound types holding source data for a pivot seems problematic since
generally all the pivot components are single-valued and, for data, often
numerical.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/json-datatype-and-table-bloat-tp5776182p5776880.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Janek Sendrowski | 2013-11-04 18:21:11 | Suitable Index for my Table |
| Previous Message | Rob Sargent | 2013-11-04 17:13:39 | Re: table lock when where clause uses unique constraing instead of primary key. |