-
Notifications
You must be signed in to change notification settings - Fork 29
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
Question: insert only stmt #32
Comments
Hi @pmpetit,
|
i give it a try, thanks also : Schema | squeeze Do you think i can use it ? |
if it is ok, i could not use it without setting a day in the cronjob, the table has 2To rows, i can not squeeze it every day... |
Also, as there is an eavy insert load on the server (12), if i understand the process, you will create a logical replication slot. But i often face this msg, if i want to create a replication slot. postgres@stock(europe)=# select * from pg_create_logical_replication_slot('slot1','pgoutput'); Thanks |
|
i try to create the replication slot manually, because i try to understand what's happening: |
Thanks for the report and for your investigation! Indeed, pg_show_plans seems to be the root cause. I've just created a report for that. |
Hello,
imagine this use case, there is only insert in the table, no updates.
i cluster the table using the pk on 2 fields "store,id". As there is only insert stmt, new tuple will be added in new blocks.
To get new tuple in the same order as the pk,i should re-run 'cluster'.
How pg_squeeze could see that it have to squeeze, without being able to use 'free_space_extra' threshold ? because old block are 100 % full (no fillfactor on the table) ?
thanks
The text was updated successfully, but these errors were encountered: