Re: [PING] fallocate() causes btrfs to never compress postgresql files - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [PING] fallocate() causes btrfs to never compress postgresql files
Date
Msg-id CA+hUKGL6V2Xsp7D1=sqwAesyPfB-Mt+aF1qDqXUPPfrFf72Lng@mail.gmail.com
Whole thread Raw
In response to [PING] fallocate() causes btrfs to never compress postgresql files  (Dimitrios Apostolou <jimis@gmx.net>)
List pgsql-hackers
Or for a completely different approach: I wonder if ftruncate() would
be more efficient on COW systems anyway.  The minimum thing we need is
for the file system to remember the new size, 'cause, erm, we don't.
All the rest is probably a waste of cycles, since they reserve real
space (or fail to) later in the checkpointer or whatever process
eventually writes the data out.



pgsql-hackers by date:

Previous
From: Daniil Davydov
Date:
Subject: Re: Speedup truncations of temporary relation forks
Next
From: Tomas Vondra
Date:
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files