| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alexander Kass <alexander(dot)kass(at)jetbrains(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: No xmin in pg_database |
| Date: | 2021-09-02 12:14:28 |
| Message-ID: | ceb3ee0058fc8d0cf5bf243e46a65eacd0ff56ce.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2021-09-02 at 12:10 +0300, Alexander Kass wrote:
> As for xmin usage, we have a working scheme. We fetch objects based on
> dbage(xid), starting from the oldest uncommitted transaction of
> previous synchronization.
> Do you think it does not work?
I don't know what exactly you are doing, so I cannot be certain.
age(xmin) will not necessarily tell you how many transactions
ago the row was created...
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Tice | 2021-09-02 12:27:43 | Re: datfrozenxid not dropping after vacuum |
| Previous Message | balasubramanian c r | 2021-09-02 11:09:09 | Querying a table with jaccard similarity with 1.6 million records take 12 seconds |