From: Rob Sargent <robjsargent@gmail.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: nextval per counted
Date: Fri, 27 Jan 2023 14:41:04 -0700
Message-ID: <4651a0e5-9ef4-f09f-067a-36907e34a1e4@gmail.com> (raw)
In-Reply-To: <CAKFQuwak+keGXCFUVftQeun+6iSDj7FJKL0gHtLHBKWtiQC_WQ@mail.gmail.com>
References: <71aa4ae1-f789-485a-ae58-2acec9aa2df0@gmail.com>
<CAKFQuwaUV3L95TzJL8rtsvcNg24ZOayMOezFJME5Gdygfxi5Zg@mail.gmail.com>
<68161326-65af-ee8b-0c9e-be5d8f0b4f7b@gmail.com>
<CAKFQuwak+keGXCFUVftQeun+6iSDj7FJKL0gHtLHBKWtiQC_WQ@mail.gmail.com>
On 1/27/23 14:31, David G. Johnston wrote:
> On Fri, Jan 27, 2023 at 2:25 PM Rob Sargent <robjsargent@gmail.com> wrote:
>
> On 1/27/23 14:20, David G. Johnston wrote:
>> On Fri, Jan 27, 2023 at 1:59 PM Rob Sargent
>> <robjsargent@gmail.com> wrote:
>>
>> I'm trying to craft SQL to invoke a sequence nextval once per
>> grouped value.
>>
>>
>> This seems like a very unusual usage of nextval/sequences...
>>
>> with cleanup as (
>> select DISTINCT e.ma <http://e.ma;, coalesce(e.pa <http://e.pa;,
>> 'fix') as pa from ...
>> ), compute as (
>> select ma, pa, nextval(...) from cleanup
>> )
>> select * from compute ... -- do whatever else you want
>>
>> So far I have this:
>>
>> with husb as(
>> select e.ma <http://e.ma;, count(distinct coalesce(e.pa
>> <http://e.pa;, nextval('egogen')::text)) as mates
>> from emp_all_by3 e group by e.ma <http://e.ma; order by mates
>> )
>> select mates, count(*)
>> from husb
>> group by mates order by mates desc;
>>
>> Your "order by mates" in the CTE is totally pointless and wasting
>> resources.
>>
>> David J.
>>
> Yeah, it wasn't when that was the last bit executed...
>
> Seems asking a sequence for an id isn't too unusual? Or are they
> specifically intended for primary keys?
>
>
> Yes, their design is excellent for surrogate primary keys. I don't
> even know what to call what you are doing but it isn't that. It seems
> like some form of counting but stuff like "row_number" and "count"
> perform that function. I don't think I'd trust using them as a
> counter...for that I'd do counting in the query then have a separate
> aspect, in user-space, not the system catalogs, that increments a counter.
>
> David J.
>
Yeah, in this case I'm actually trying to assign an id in place of a
null, but only one id for all null for one ma. One thought was to
simply use the "ma" value but the table constraints are such that that
cannot be.
TL/DR
This is pedigree ego/ma/pa triplet work. Set of ego with a mother and
missing father can be considered a sibship (one mother/father pair) or a
"half-sibship" where each child get assigned a unique father (one
mother/N fathers). In that latter case, the sequence works perfectly.
We don't allow for mother/mother, the analysis tools are not up for that
(yet).
Thanks for your time,
rjs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: robjsargent@gmail.com, david.g.johnston@gmail.com
Subject: Re: nextval per counted
In-Reply-To: <4651a0e5-9ef4-f09f-067a-36907e34a1e4@gmail.com>
References: <71aa4ae1-f789-485a-ae58-2acec9aa2df0@gmail.com> <CAKFQuwaUV3L95TzJL8rtsvcNg24ZOayMOezFJME5Gdygfxi5Zg@mail.gmail.com> <68161326-65af-ee8b-0c9e-be5d8f0b4f7b@gmail.com> <CAKFQuwak+keGXCFUVftQeun+6iSDj7FJKL0gHtLHBKWtiQC_WQ@mail.gmail.com> <4651a0e5-9ef4-f09f-067a-36907e34a1e4@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox