| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Persist MVCC forever - retain history |
| Date: | 2020-07-03 13:57:55 |
| Message-ID: | CAMjNa7cvuwNk1zKWJzhTEJsOhnYcefxHTvREVVTu+AaXZ_XDdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> But I didn't fill a big interest to it from community.
Just fyi, it is something that I use in my database design now (just hacked
together using ranges / exclusion constraints) and
would love for a well supported solution.
I've chimed in a couple times as this feature has popped up in discussion
over the years, as I have seen others with similar needs do as well.
Just sometimes feels like spam to chime in just saying "i'd find this
feature useful" so I try and not do that too much. I'd rather not step on
the
community's toes.
-Adam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-07-03 14:04:10 | Re: warnings for invalid function casts |
| Previous Message | Tom Lane | 2020-07-03 13:52:19 | Re: Cleanup - Removed unused function parameter in reorder buffer & parallel vacuum |