From: | Thorsten Schöning <tschoening(at)am-soft(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to properly query lots of rows based on timestamps? |
Date: | 2020-08-30 13:36:22 |
Message-ID: | 89673594.20200830153622@am-soft.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Guten Tag Tom Lane,
am Samstag, 29. August 2020 um 17:19 schrieben Sie:
> TBH, this seems like a pretty awful data design. If you included the
> timestamp column into oms_rec, and had an index on it, then you would
> not need a join at all.
clt_rec and oms_rec are different types of data and only the former
includes the timestamp, that's simply how the stored data works. So if
at all, oms_rec needs to be embedded into clt_rec entirely. While I
considered that in the past already, wasn't sure if that is the best
approach to model those two different data types.
I'll make a note and consider refactoring at some point, so thanks for
your opinion!
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: Thorsten(dot)Schoening(at)AM-SoFT(dot)de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
From | Date | Subject | |
---|---|---|---|
Next Message | Thorsten Schöning | 2020-08-30 13:54:11 | Re: How to properly query lots of rows based on timestamps? |
Previous Message | Thomas Boussekey | 2020-08-29 19:18:06 | Re: When are largobject records TOASTed into pg_toast_2613? |