Hi,
Please don't cross post to multiple lists.
On Thu, Nov 15, 2018 at 08:53:14PM +0200, Mariel Cherkassky wrote:
> Can someone explain the logic behind it ? I know that vacuum full isnt
> something recommended but I found out that whenever I run vacuum full on my
> database checkpoint occurs dur
Hi
> I mean basicly the wals should contain the changes, and vacuum full changes
> the location of the data and not actually the data.
Row location is data. For example, index lookup relies on TID (tuple id, hidden
ctid column) - physical row address in datafile.
Postgresql WAL - it is about phy
First of all thank you for the quick answer. In my case checkpoint happened
every one second during the vacuum full so the checkpoint timeout isn't
relevant. My guess was that it writes the changes to the wals but I didn't
find anything about it in the documentation. Can you share a link that
prove
Hi
Checkpoint can be occurs due timeout (checkpoint_timeout) or due amount of WAL
(max_wal_size).
Vacuum full does write all data through WAL and therefore may trigger
checkpoint more frequently.
regards, Sergei
Hi,
Can someone explain the logic behind it ? I know that vacuum full isnt
something recommended but I found out that whenever I run vacuum full on my
database checkpoint occurs during that time every second ! well I know that
VACUUM FULL duplicates the data into new data files and then it deletes
