Hello,
I encountered an issue while attempting to reclaim space from a heavily bloated
table:
Initial analysis using
https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
indicated approximately 600GB of bloat in the table.
I initiated a VACUUM FULL operation to r
Hello,
It seems that I am running into this issue as well.
Is it likely that this would ever be a config option?
Best,
Pierre Barre
On Fri, May 3, 2024, at 05:11, Riku Iki wrote:
> I did the testing and confirmed that this was the issue.
>
> I run following query:
>
> cr
NFS directly.
Best,
Pierre
On Fri, Jul 18, 2025, at 06:40, Laurenz Albe wrote:
> On Fri, 2025-07-18 at 00:57 +0200, Pierre Barre wrote:
>> Looking forward to your feedback and questions!
>
> I think the biggest hurdle you will have to overcome is to
> convince notorio
Hi everyone,
I wanted to share a project I've been working on that enables PostgreSQL to run
on S3 storage while maintaining performance comparable to local NVMe. The
approach uses block-level access rather than trying to map filesystem
operations to S3 objects.
ZeroFS: https://github.com/Barr
ormance in that case :)
>
> Cheers,
> Seref
>
>
> On Fri, Jul 18, 2025 at 11:58 AM Pierre Barre wrote:
>> __
>> Hi Seref,
>>
>> For the benchmarks, I used Hetzner's cloud service with the following setup:
>>
>> - A Hetzner s3 bucket in th
fy how exactly you're running
> postgres in your tests? A specific AWS service? What's the test
> infrastructure that sits above the file system?
>
> On Thu, Jul 17, 2025 at 11:59 PM Pierre Barre wrote:
>> Hi everyone,
>>
>> I wanted to share a project I
ri, Jul 18, 2025, at 12:57, Pierre Barre wrote:
> Hi Seref,
>
> For the benchmarks, I used Hetzner's cloud service with the following setup:
>
> - A Hetzner s3 bucket in the FSN1 region
> - A virtual machine of type ccx63 48 vCPU 192 GB memory
> - 3 ZeroFS nbd devices (sam
