agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: David Johnston <polobo@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: Re: how to effectively SELECT new "customers"
Date: Fri, 28 Feb 2014 08:33:09 -0800 (PST)
Message-ID: <1393605189189-5794066.post@n5.nabble.com> (raw)
In-Reply-To: <1083597622.602688.1393603940121.JavaMail.root@mobiletech.sk>
References: <1001132708.567696.1393510818245.JavaMail.root@mobiletech.sk>
<1393513774376-5793882.post@n5.nabble.com>
<976203811.595346.1393587926835.JavaMail.root@mobiletech.sk>
<1393601978985-5794056.post@n5.nabble.com>
<1083597622.602688.1393603940121.JavaMail.root@mobiletech.sk>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
Jan Ostrochovsky wrote
> customer may have various payment channels during the time... new-ness is
> not impacted by the channel, it does not matter from which channel, all
> customer_id occurences count (in determined filtration criteria, e.g.
> town, service, subservice)
>
> and there are also other filtration and grouping criteria (town, service,
> subservice) and user of reporting tool should have possibility to select
> from those... there are dozens of services and subservices, cca 4 payment
> channels, dozens of towns... therefore preprocessing through materialized
> view (if I understand your suggestion correctly), would contain a lot of
> combinations, it seems quite complex for me in these circumstances
>
> I also considered WITH (CTEs) previously, I will rethink it yet, after
> these your recommendations
I'm not sure what you are going for since you keep adding additional
criteria/constraints to your problem. At this point you are faced with a
series of trade-offs between caching, speed, and flexibilty, complexity. I
would suggest you break up your requirements into smaller pieces and not go
looking for some kind of magic bullet that will solve all your problems in a
single query. It likely does not exist.
I would also suggest that you look into resources on data warehousing and
the star schema; doing what you are trying directly within the OLTP is
probably not the best solution - especially not on front-end servers. My
experience in this area is thin but maybe someone else can make some
suggestions and/or provide some useful resource links.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/how-to-effectively-SELECT-new-customers-tp5793867p5794066.ht...
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (10+ messages) latest in thread
Message-ID: <1393605189189-5794066.post@n5.nabble.com>
Permalink: ../1393605189189-5794066.post@n5.nabble.com/
Also on: postgresql.org/message-id/1393605189189-5794066.post@n5.nabble.com
reply
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: polobo@yahoo.com
Subject: Re: how to effectively SELECT new "customers"
In-Reply-To: <1393605189189-5794066.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox