On 05/21/2015 01:39 PM, Andres Freund wrote:
On 2015-05-21 11:54:40 -0700, Josh Berkus wrote:
This has been talked about as a feature, but would require major work on
PostgreSQL to make it possible. You'd be looking at several months of
effort by a really good hacker, and then a whole bunch
On 04/23/2015 12:47 PM, Jan Gunnar Dyrset wrote:
I think that preallocating lumps of a given, configurable size, say 4
MB, for the tables would remove this problem. The max number of
fragments on a 1 GB file would then be 250, which is no problem. Is
this possible to configure in PostgreSQL?
On 2015-05-21 11:54:40 -0700, Josh Berkus wrote:
This has been talked about as a feature, but would require major work on
PostgreSQL to make it possible. You'd be looking at several months of
effort by a really good hacker, and then a whole bunch of performance
testing. If you have the
It may be even easier. AFAIR, it's possible just to tell OS expected
allocation without doing it. This way nothing changes for general code,
it's only needed to specify expected file size on creation.
Please see FILE_ALLOCATION_INFO:
On 2015-04-29 10:06:39 +0200, Andres Freund wrote:
Hi,
On 2015-04-23 19:47:06 +, Jan Gunnar Dyrset wrote:
I am using PostgreSQL to log data in my application. A number of rows
are added periodically, but there are no updates or deletes. There are
several applications that log to
Hi,
On 2015-04-23 19:47:06 +, Jan Gunnar Dyrset wrote:
I am using PostgreSQL to log data in my application. A number of rows
are added periodically, but there are no updates or deletes. There are
several applications that log to different databases.
This causes terrible disk
On 04/29/2015 01:08 AM, Andres Freund wrote:
Which OS and filesystem is this done on? Because many halfway modern
systems, like e.g ext4 and xfs, implement this in the background as
'delayed allocation'.
Oh, it's in the subject. Stupid me, sorry for that. I'd consider testing
how much better
On Wed, Apr 29, 2015 at 07:07:04AM -0700, Joshua D. Drake wrote:
On 04/29/2015 01:08 AM, Andres Freund wrote:
Which OS and filesystem is this done on? Because many halfway modern
systems, like e.g ext4 and xfs, implement this in the background as
'delayed allocation'.
Oh, it's in the
On 04/29/2015 10:35 AM, k...@rice.edu wrote:
On Wed, Apr 29, 2015 at 07:07:04AM -0700, Joshua D. Drake wrote:
On 04/29/2015 01:08 AM, Andres Freund wrote:
Which OS and filesystem is this done on? Because many halfway modern
systems, like e.g ext4 and xfs, implement this in the background as
I am using PostgreSQL to log data in my application. A number of rows are added
periodically, but there are no updates or deletes. There are several
applications that log to different databases.
This causes terrible disk fragmentation which again causes performance
degradation when retrieving
10 matches
Mail list logo
