Skip to content

Human-readable changeset #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gsmolk opened this issue Jun 11, 2020 · 1 comment · Fixed by #6
Closed

Human-readable changeset #1

gsmolk opened this issue Jun 11, 2020 · 1 comment · Fixed by #6
Assignees
@ololobus
Labels
enhancement New feature or request
Milestone
Ptrack 2.2.0

Comments

@gsmolk
Copy link

gsmolk commented Jun 11, 2020

It would be useful to determine how much of instance has mutated since arbitrary point in time
@ololobus ololobus changed the title human-readable changeset Human-readable changeset Apr 21, 2021
@ololobus ololobus added the enhancement New feature or request label Apr 21, 2021
@ololobus ololobus added this to the Ptrack 2.2.0 milestone Apr 21, 2021
@ololobus ololobus self-assigned this Apr 21, 2021
@ololobus ololobus mentioned this issue Apr 22, 2021
Merged
@ololobus
Copy link
Contributor

ololobus commented Apr 22, 2021 •
edited
Loading

Added ptrack_get_change_stat() in the PR:

=# select * from ptrack_get_change_stat('13/A970F418');
 files | pages |      size, MB      
-------+-------+--------------------
    12 |   144 | 1.1250000000000000
(1 row)

ololobus added a commit that referenced this issue May 16, 2021
@ololobus
Merge pull request #6 from postgrespro/double_slot
708c8e2 
Resolve issues #5 and #1: reduce number of collisions in the ptrack map
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ololobus ololobus

Labels
enhancement New feature or request
Projects
None yet
Milestone
Ptrack 2.2.0
Development

Successfully merging a pull request may close this issue.

Resolve issues #5 and #1: reduce number of collisions in the ptrack map postgrespro/ptrack
2 participants
@ololobus @gsmolk