Amount of time FULL VACUUM/VACUUM The 2019 Stack Overflow Developer Survey Results Are In ...
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
If the empty set is a subset of every set, why write ... ∪ {∅}?
What information about me do stores get via my credit card?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Why can't wing-mounted spoilers be used to steepen approaches?
In horse breeding, what is the female equivalent of putting a horse out "to stud"?
Match Roman Numerals
How to grep and cut numbers from a file and sum them
Can smartphones with the same camera sensor have different image quality?
How do you keep chess fun when your opponent constantly beats you?
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
What are these Gizmos at Izaña Atmospheric Research Center in Spain?
What do you call a plan that's an alternative plan in case your initial plan fails?
Arduino Pro Micro - switch off LEDs
When did F become S in typeography, and why?
How to copy the contents of all files with a certain name into a new file?
How to test the equality of two Pearson correlation coefficients computed from the same sample?
First use of “packing” as in carrying a gun
Is this wall load bearing? Blueprints and photos attached
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
Is there a writing software that you can sort scenes like slides in PowerPoint?
Can undead you have reanimated wait inside a portable hole?
Simulating Exploding Dice
Segmentation fault output is suppressed when piping stdin into a function. Why?
Amount of time FULL VACUUM/VACUUM
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Partial vacuum and whole table vacuumHow much time will a vacuum/autovacuum operation take?TOAST Table Growth Out of Control - FULLVAC Does NothingPostgreSQL difference between VACUUM FULL and CLUSTERPostgreSQL 9.2 (PostGIS) performance problemVACUUM FREEZE vs. VACUUM FULLPostgreSQL, UPDATE CASE statement uses huge amount of spaceDoes VACUUM FULL need ANALYZETime taken by VACUUM FULL to reclaim spacePostgres Transaction ID Wraparound and Autovacuum
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a table "lng_grid_test", which, at the beginning, had around 600 000 000 around. The table is defined as :
-- Table: public.lng_grid_test
-- DROP TABLE public.lng_grid_test;
CREATE TABLE public.lng_grid_test
(
gid integer NOT NULL DEFAULT nextval('lng_grid_test_gid_seq'::regclass),
geom geometry(LineString,4326),
CONSTRAINT lng_grid_test_pkey PRIMARY KEY (gid)
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.lng_grid_test
OWNER TO postgres;
-- Index: public.lng_grid_test_idx
-- DROP INDEX public.lng_grid_test_idx;
CREATE INDEX lng_grid_test_idx
ON public.lng_grid_test
USING gist
(geom);
I applied to delete request to this table, reducing the rows to around 490 000 000.
Before processing any further, I thought it would be accurate to execute a vaccum.
So I am currently running a vacuum,
INFO: exécution du VACUUM sur « public.lng_grid_test »
INFO: « lng_grid_test » : 3588177 versions de ligne supprimables, 485535819 non supprimables
parmi 5042516 pages
DETAIL: 0 versions de lignes ne peuvent pas encore être supprimées.
CPU 106.20s/230.72u sec elapsed 402.26 sec.
Do you think I should stop the full vacuum process and just chose the vacuum with analyze and freeze options or should I keep running the vacuum? And, if you think I should keep on running the process, what may be the order of time it will take to finish the vacuum?
Because I can't work on the table and I don't have a clue about how many time it will take to finish the vacuum.
Thank you!
postgresql vacuum
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a table "lng_grid_test", which, at the beginning, had around 600 000 000 around. The table is defined as :
-- Table: public.lng_grid_test
-- DROP TABLE public.lng_grid_test;
CREATE TABLE public.lng_grid_test
(
gid integer NOT NULL DEFAULT nextval('lng_grid_test_gid_seq'::regclass),
geom geometry(LineString,4326),
CONSTRAINT lng_grid_test_pkey PRIMARY KEY (gid)
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.lng_grid_test
OWNER TO postgres;
-- Index: public.lng_grid_test_idx
-- DROP INDEX public.lng_grid_test_idx;
CREATE INDEX lng_grid_test_idx
ON public.lng_grid_test
USING gist
(geom);
I applied to delete request to this table, reducing the rows to around 490 000 000.
Before processing any further, I thought it would be accurate to execute a vaccum.
So I am currently running a vacuum,
INFO: exécution du VACUUM sur « public.lng_grid_test »
INFO: « lng_grid_test » : 3588177 versions de ligne supprimables, 485535819 non supprimables
parmi 5042516 pages
DETAIL: 0 versions de lignes ne peuvent pas encore être supprimées.
CPU 106.20s/230.72u sec elapsed 402.26 sec.
Do you think I should stop the full vacuum process and just chose the vacuum with analyze and freeze options or should I keep running the vacuum? And, if you think I should keep on running the process, what may be the order of time it will take to finish the vacuum?
Because I can't work on the table and I don't have a clue about how many time it will take to finish the vacuum.
Thank you!
postgresql vacuum
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a table "lng_grid_test", which, at the beginning, had around 600 000 000 around. The table is defined as :
-- Table: public.lng_grid_test
-- DROP TABLE public.lng_grid_test;
CREATE TABLE public.lng_grid_test
(
gid integer NOT NULL DEFAULT nextval('lng_grid_test_gid_seq'::regclass),
geom geometry(LineString,4326),
CONSTRAINT lng_grid_test_pkey PRIMARY KEY (gid)
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.lng_grid_test
OWNER TO postgres;
-- Index: public.lng_grid_test_idx
-- DROP INDEX public.lng_grid_test_idx;
CREATE INDEX lng_grid_test_idx
ON public.lng_grid_test
USING gist
(geom);
I applied to delete request to this table, reducing the rows to around 490 000 000.
Before processing any further, I thought it would be accurate to execute a vaccum.
So I am currently running a vacuum,
INFO: exécution du VACUUM sur « public.lng_grid_test »
INFO: « lng_grid_test » : 3588177 versions de ligne supprimables, 485535819 non supprimables
parmi 5042516 pages
DETAIL: 0 versions de lignes ne peuvent pas encore être supprimées.
CPU 106.20s/230.72u sec elapsed 402.26 sec.
Do you think I should stop the full vacuum process and just chose the vacuum with analyze and freeze options or should I keep running the vacuum? And, if you think I should keep on running the process, what may be the order of time it will take to finish the vacuum?
Because I can't work on the table and I don't have a clue about how many time it will take to finish the vacuum.
Thank you!
postgresql vacuum
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
I have a table "lng_grid_test", which, at the beginning, had around 600 000 000 around. The table is defined as :
-- Table: public.lng_grid_test
-- DROP TABLE public.lng_grid_test;
CREATE TABLE public.lng_grid_test
(
gid integer NOT NULL DEFAULT nextval('lng_grid_test_gid_seq'::regclass),
geom geometry(LineString,4326),
CONSTRAINT lng_grid_test_pkey PRIMARY KEY (gid)
)
WITH (
OIDS=FALSE
);
ALTER TABLE public.lng_grid_test
OWNER TO postgres;
-- Index: public.lng_grid_test_idx
-- DROP INDEX public.lng_grid_test_idx;
CREATE INDEX lng_grid_test_idx
ON public.lng_grid_test
USING gist
(geom);
I applied to delete request to this table, reducing the rows to around 490 000 000.
Before processing any further, I thought it would be accurate to execute a vaccum.
So I am currently running a vacuum,
INFO: exécution du VACUUM sur « public.lng_grid_test »
INFO: « lng_grid_test » : 3588177 versions de ligne supprimables, 485535819 non supprimables
parmi 5042516 pages
DETAIL: 0 versions de lignes ne peuvent pas encore être supprimées.
CPU 106.20s/230.72u sec elapsed 402.26 sec.
Do you think I should stop the full vacuum process and just chose the vacuum with analyze and freeze options or should I keep running the vacuum? And, if you think I should keep on running the process, what may be the order of time it will take to finish the vacuum?
Because I can't work on the table and I don't have a clue about how many time it will take to finish the vacuum.
Thank you!
postgresql vacuum
postgresql vacuum
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
edited Jan 8 '18 at 7:33
a_horse_with_no_name
41.7k779116
41.7k779116
asked Jun 16 '16 at 12:52
user37103user37103
1
asked Jun 16 '16 at 12:52
user37103user37103
1
asked Jun 16 '16 at 12:52
user37103user37103
1
1
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should never stop a vacuum process, ever.
A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f141416%2famount-of-time-full-vacuum-vacuum%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should never stop a vacuum process, ever.
A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
add a comment |
You should never stop a vacuum process, ever.
A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
add a comment |
You should never stop a vacuum process, ever.
A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
You should never stop a vacuum process, ever.
A vacuum full will completely recreate the table, so it should take roughly as long to run as it would to create and populate a brand new table and index it with all 490_000_000 records.
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
edited Jun 16 '16 at 13:43
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
answered Jun 16 '16 at 13:15
PhilHibbsPhilHibbs
326214
326214
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
add a comment |
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
Ok it's finished, it took around 5 hours so I hope it will be usefull.
– user37103
Jun 16 '16 at 13:38
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
You may cancel the vacuum, it doesn't do anything bad. But of course you must not terminate the process badly.
– Sami Kuhmonen
Jun 16 '16 at 14:11
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f141416%2famount-of-time-full-vacuum-vacuum%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
