| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Struggling with EXCLUDE USING gist |
| Date: | 2021-06-04 18:26:50 |
| Message-ID: | 541a4f52-3e11-1d75-741a-daa54b48af19@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 6/4/21 1:32 PM, Laura Smith wrote:
> What is the solution then ? I need to keep historical versions but
> at the same time I need a "current" version. If I am not able to use
> "infinity" as bounds for "current" version then clearly I'm wasting
> my time trying to use EXCLUDE AS for version tracking because clearly
> using fixed timestamps instead of "infinity" for tstzrange would be a
> hacky fix that will be fragile and prone to breakage.
This is not exactly the same thing you are trying to do (I think), but
maybe you can get some useful ideas from this:
https://www.joeconway.com/presentations/RLS_TimeTravel-FOSDEM2019.pdf
HTH,
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laura Smith | 2021-06-04 18:31:42 | Re: Struggling with EXCLUDE USING gist |
| Previous Message | Adrian Klaver | 2021-06-04 18:21:48 | Re: Struggling with EXCLUDE USING gist |