-
Notifications
You must be signed in to change notification settings - Fork 67
pg_pathman creates thousands partitions #16
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.
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
Comments
"prices_4373" now and it's empty |
Had to drop table, cause server went to restart loop with many warnings:
|
Hi @SonicGD,
Could you remember were there any warnings or errors before you inserted new rows? Do you use x86-64 architecture or something else?
A dump of original table would be helpful : ) It'll be great if you could upload dump somewhere on dropbox or google drive! |
And if you could reproduce (or still have) problem, a dump of partitions could be helpful as well |
Looks like there's nothing more to discuss at the moment. Feel free to give us a feedback in case you're in trouble. |
Hello! Today for the second time we faced strange pg_pathman behavior.
Base table:
Range partition:
Before "problem" last partition was "prices_7". last record date was 1466663582. Then we insert 3 records with date=1466664722. And... pathman put them into partition "prices_2007". So we have "prices_7", 2000 empty partitions and 3 records in "prices_2007".
We dropped all empty partitions, but serveral minutes later pathman writes new records to "prices_2766" starting with date=1466665444. 722 seconds and 759 new partitions =)
Right now we have "prices_3373" and i think it will keep growing.
What can we do to help fix this problem? We have similar problem with other table in other db and fixed it by recreate whole table from scratch. I'm going to do same thing here, but if you need some additional info - it can wait for several hours.
UPD: Almost forgot versions! Postgres 9.5.3 (https://hub.docker.com/_/postgres/), pg_pathman from master (2775b5a)
The text was updated successfully, but these errors were encountered: