can also run this in a defined transaction boundary
rather than using auto-commit. Right now I am thumbing through your email
and trying it out.
Bob
On Wed, Oct 3, 2012 at 12:23 PM, Robert Buck wrote:
> Thank you, Samuel.
>
> I am trying some of this out right now...
>
> This is gr
from
> multiple tables into the same row.
>
>
>
> On Tue, Oct 2, 2012 at 12:57 PM, Samuel Gendler > wrote:
>
>>
>>
>> On Tue, Oct 2, 2012 at 2:45 AM, Robert Buck wrote:
>>
>>> Hi Samuel
>>>
>>> Thank you. This may be a bit
Hi Samuel
Thank you. This may be a bit of a stretch for you, but would it be possible for
me to peek at a sanitized version of your cross tab query, for a good example
on how to do this for this noob?
This will be pretty common in my case. The biggest tables will get much larger
as they are r
sql-ow...@postgresql.org] *On Behalf Of *Robert Buck
> *Sent:* Monday, October 01, 2012 8:47 PM
> *To:* pgsql-sql@postgresql.org
> *Subject:* [SQL] [noob] How to optimize this double pivot query?
>
> ** **
>
> I have two tables that contain key-value data that I want to combine in
&
I have two tables that contain key-value data that I want to combine in
pivoted form into a single result set. They are related to two separate
tables.
The tables are: test_results, test_variables, metric_def, metadata_key. The
latter two tables are enum-like tables, basic descriptors of data stor
