From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Selecting All Columns Associated With Maximum Value of One Column |
Date: | 2011-10-06 13:34:00 |
Message-ID: | alpine.LNX.2.00.1110060620330.26051@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 5 Oct 2011, David Johnston wrote:
> 2) "Window" - max(quant) OVER (PARTITION BY ...)
Hmm-m-m. I have a problem here emulating the example on the document page.
Regardless of which column is first after SELECT postgres tells me that
column does not exist.
select site_id, sample_date, param, max(quant) over (partition by param)
chemistry;
ERROR: column "site_id" does not exist
LINE 1: select site_id, sample_date, param, max(quant) over (partiti...
^
select str_name, site_id, sample_date, param, max(quant) over (partition by
str_name) chemistry;
ERROR: column "str_name" does not exist
LINE 1: select str_name, site_id, sample_date, param, max(quant) ove...
^
What am I doing incorrectly here?
Also, with the window function can I limit the output to a single str_name
and param?
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent de Phily | 2011-10-06 13:39:02 | Re: Never-idle autovacuum, and does (auto)vacuuming fill the OS cache ? |
Previous Message | Rich Shepard | 2011-10-06 13:13:52 | Re: Selecting All Columns Associated With Maximum Value of One Column |